Another thought..
.. following on from the previous information, what I tried doing was switching to the zabbix user ("su - zabbix") and then running zabbix-server (again, with the stop|start|restart switches) and it still says permission denied creating the .PID file. There is also no new entry in the zabbix_server.log file when doing this.
The zabbix user seems to have some sort of permissions problem - however it is confusing since during the server start up it is definitely getting further. What I mean is it seems to me that although the zabbix user account can't create the .PID (or a log file entry) when I use "su", at server start up when the zabbix_server process tries to start it definitely DOES creates a .PID file (therefore removing the previous one) AND it writes a log entry "unable to connect through myqsld.sock").
Where do I check to find out what user the zabbix_server process is trying to run under (i.e. at server boot up)?
DSon.
.. following on from the previous information, what I tried doing was switching to the zabbix user ("su - zabbix") and then running zabbix-server (again, with the stop|start|restart switches) and it still says permission denied creating the .PID file. There is also no new entry in the zabbix_server.log file when doing this.
The zabbix user seems to have some sort of permissions problem - however it is confusing since during the server start up it is definitely getting further. What I mean is it seems to me that although the zabbix user account can't create the .PID (or a log file entry) when I use "su", at server start up when the zabbix_server process tries to start it definitely DOES creates a .PID file (therefore removing the previous one) AND it writes a log entry "unable to connect through myqsld.sock").
Where do I check to find out what user the zabbix_server process is trying to run under (i.e. at server boot up)?
DSon.
Comment