Hey folks,

Been trying to make this vmware appliance work. The time I have spent repairing it I probably should have spent installing it on my own distro. Ho Hum!

I am down to my final problem.

In /home/proxylizer there sits a file called mysql.pipe

If this file has wrong permissions then you will see in /var/log/proxylizer/webproxytodb_debug.log an error that says cannot access the file.

So, I found the file with ownership of root:adm when I first installed. And nothing works.

When I change that ownership to proxylizer:proxylizer things start to work.

HOWEVER, and this is my quesiton: If ever I reboot the server some process resets the ownership of that file back to root:adm and proxylizer stops working.

Does any body know what process does that, and where the script is located so I can try to modify it?

Now this is clearing up I see another error in the debug log. Invalid IP address. Some more verbosity in those logs would help! Sigh.

P.s. I am not an SQL guy at all....

Regards

Alex

Look at /etc/syslog-ng/syslog-ng.conf file. You have to change permissions in the sections:
#default owner, group, and permissions for log files
#default owner, group, and permissions for created directories
to 0777. After that restart syslog-ng or just reboot your VM. mysql.pipe is going to have 777 permissions.
Also, have a look at /home/proxylizercrontab file. It supposed to have root as the owner and, as a result, it won't start under proxylizer account(cause it doesn't has permissions for being executed by the other users). So you have to change the owner to "proxylizer" or, just as I did, change permissions to 777.

P.S. I'm not in touch with Linux, actually. And i spend the hole day before I found what problem was it in. I think Proxylizer support could tell the community about such kind of mistake in their VM image. There're a lot of questions in this board about problems with the image, and almost all of them comes because of wrong file permissions.