|Subject:||Re: Problem starting my monit|
|Date:||Wed, 16 May 2012 08:37:44 +0200|
the whole problem is very simple, you just need to see the things in context and understand the relationships:
1.) if monit is configured just with the SysV init scripts (/etc/init.d/monit) and no Upstart, then if monit will stop nothing will try to restart it. The "monit quit" can be used, as there is no supervisor which needs to be notified.
2.) or if monit is configured with inittab - init will always respawn it on monit stop and there is no way to stop monit (other then unconfiguring it from inittab)
3.) or if monit is configured with Upstart, monit start/stop needs to be performed via Upstart only. If monit will die or will be stopped via "monit quit" (outside of upstart control), then Upstart will restart it.
You should go only with one of these methods - not combine them.
If you think you configured monit with Upstart AND Upstart doesn't start monit when you stop it with "monit quit" or simply kill monit, then you have problem in your Upstart configuration - go troubleshoot your Upstart settings (see Upstart documentation for how to do it). The Upstart configuration for monit which is on the wiki page works => you have some problem with Upstart in general or messed the init/inittab/upstart configurations.
In real life monit doesn't stop unless instructed - the spurious stop could be caused by crash (due to some bug). The monit can be stopped only by the person who has privilege to do it (the user under which monit is running).
On May 16, 2012, at 8:21 AM, sukbir singh wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|