Hide Forgot
The server pid file is named "zabbix". PID files should be called the same as the binary, as far as the FHS says. Looking at http://fedoraproject.org/wiki/Packaging:SysVInitScript, the lock files should be called the same as the service. Everything is fine for the agent, but the server and proxy files are named wrong. Actual names: - Server PID: zabbix.pid - Server lock file: zabbix - Proxy PID: zabbix_proxy.pid Expected names: - Server PID: zabbix_server_mydatabasesystem.pid - Server lock file: zabbix-server - Proxy PID: zabbix_proxy_mydatabasesystem.pid
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This ticket is a left-over from the Fedora init scripts period. The situation exactly matches what we had in EPEL6 and 5 under the name of zabbix and zabbix20 until recently though. With the use of the Alternatives system and overhauled init scripts the situation in 1.8.10-1 and 2.0.10-2 builds is now: Init scripts: zabbix-agent zabbix-server zabbix-proxy Lock files: zabbix-agent zabbix-server zabbix-proxy PID files: zabbix_agentd.pid zabbix_server.pid zabbix_proxy.pid The PID file names now match the process names, the lock file names match the init script names. Thus this issue is settled.