|Subject:||Application Not getting monitored on improper reboot|
|Date:||Mon, 28 Nov 2005 18:32:58 +0530|
We are using monit software for the last 6 months and it has been very useful for all of us. Thanks to all who made this a huge succes.
I would really appreciate your help with following problem:
I am using monit V4.4 to monitor a list of services.
On a running system, if some services cannot be restarted for some reason, I specify in the /etc/monitrc file to retry a number of times, before 'timeout'. After a specified number of retries (in the /etc/monitrc file), monit shows that it will give up monitoring the system.
For example, I have a service called foobar, which failed to start multiple times (5 times in this case), and exceeded the limit I specified in the /etc/monitrc file:
check process foobar
with pidfile "/var/run/foobar.pid"
start program = "/etc/rc.d/init.d/foobar start"
stop program = "/etc/rc.d/init.d/foobar stop"
if 5 restarts within 6 cycles then timeout
We are calling "monit monitor all" immediately after starting monit to start monitoring all the applications (including timed out ones) once a reboot occurs.
But incase of a abnormal/abrupt reboot, i.e When you poweroff the system directly or if you press reset button(Improper reboot), the monit is not monitoring the timed out applications.
Only if we forcibly the state file that monit maintains in user's home directory i.e $home/.monit.state, I am able to remonitor the timed out applcations. Is there any other way to remonitor these services?
What could be the problem? I failed to find something useful in Google :(
Thanks in advance!
Thanks and Regards,
|[Prev in Thread]||Current Thread||[Next in Thread]|