zabbix 2.0.5 (and 2.0.4-r1 too) conf file for zabbix_proxy has a invalid setting: AlertScriptsPath This setting is available only for zabbix_server, zabbix_proxy doesn't support it. It should be removed from the default /etc/zabbix/zabbix_proxy.conf file.
I'll look into this when making a planned bump next week.
I had reproduced the bug and is same for me, and in the next release 2.0.6 is also same. actual result: gentoo-test zabbix # /etc/init.d/zabbix-proxy start * Starting Zabbix proxy ... zabbix_proxy [13623]: unknown parameter [AlertScriptsPath] in config file [/etc/zabbix/zabbix_proxy.conf], line 136 * start-stop-daemon: failed to start `/usr/sbin/zabbix_proxy' [ !! ] * ERROR: zabbix-proxy failed to start expected result: /etc/init.d/zabbix-proxy start * Starting Zabbix proxy ... [ ok ]
Created attachment 346944 [details, diff] linking to proxy 2.0 config file
Created attachment 346946 [details] zabbix 2.0.x config file
2.0.6 is still package masked. This bug is just one of the issues being worked on before it is put in testing arch.
Fixed in zabbix 2.0.6-r3 which was just committed to cvs.
tested on x86_64 the zabbix_proxy config file now is correct and is not triggering any warning
oh i forget to mention, is a good idea to change the configuration file if you want to use pid file. for exemple if you use the default configuration file, the init.d file will work buy complain about the absence of the pid file (present for zabbix_agent and zabbix_server). actual result: gentoo-test ~ # /etc/init.d/zabbix-proxy restart * Caching service dependencies ... [ ok ] * Stopping Zabbix agent ... * start-stop-daemon: fopen `/var/run/zabbix/zabbix_proxy.pid': No such file or directory [ ok ] * Starting Zabbix agent ... [ ok ] expected result: gentoo-test ~ # /etc/init.d/zabbix-proxy restart * Stopping Zabbix agent ... [ ok ] * Starting Zabbix agent ... [ ok ] so i can suggest to give a default configuration file with pid already enable or it will complain... adding: PidFile=/var/run/zabbix/zabbix_proxy.pid
