Hi,
I allready had some discution here about the way zabbix_server start. HHere is the problem i meet, perhaps some of you can help me
I tried to tweak the scripts and use the daemon tool supervise with zabbix. In all case i meet a problem. It seems that zabbix just start his process and fork a new one leaving the started one so supervise cannot restart it in case of failure.
The daemon tools have for this case a hack that we see here :
How can I supervise a daemon that puts itself into the background? When I run inetd, my shell script exits immediately, so supervise keeps trying to restart it.
Answer: The best answer is to fix the daemon. Having every daemon put itself into the background is bad software design.
fghack can force some daemons to run in the foreground:
#!/bin/sh
echo starting
exec fghack inetd
Beware that supervise cannot send signals to daemons under fghack.
But fghack does not work for zabbix.
I was wondering if there was an option to the command line to prevent zabbix to go in foreground or anything like that in the configuration file. Anyone made this work ? I'de like to have supervise restart the daemon in case of failure
regards,
Ghislain.
I allready had some discution here about the way zabbix_server start. HHere is the problem i meet, perhaps some of you can help me

I tried to tweak the scripts and use the daemon tool supervise with zabbix. In all case i meet a problem. It seems that zabbix just start his process and fork a new one leaving the started one so supervise cannot restart it in case of failure.
The daemon tools have for this case a hack that we see here :
How can I supervise a daemon that puts itself into the background? When I run inetd, my shell script exits immediately, so supervise keeps trying to restart it.
Answer: The best answer is to fix the daemon. Having every daemon put itself into the background is bad software design.
fghack can force some daemons to run in the foreground:
#!/bin/sh
echo starting
exec fghack inetd
Beware that supervise cannot send signals to daemons under fghack.
But fghack does not work for zabbix.
I was wondering if there was an option to the command line to prevent zabbix to go in foreground or anything like that in the configuration file. Anyone made this work ? I'de like to have supervise restart the daemon in case of failure
regards,
Ghislain.
Comment