and let monit start them.
By default the monitoring mode is automatic which will enable
monitoring of all service by default and if the service is not
running, it will start it. The "start all" command is thus not
necessary unless you have some services in manual monitoring mode.
There are important fixes in upcoming monit-5.0 (you can get beta
It fixes the described race condition where monit tried to start
service but before the start was finished, the monitoring thread
detected that the service is not running and tried to restart it
parallel to pending start action).
On Jan 21, 2009, at 8:47 PM, Gilad Benjamini wrote:
I am trying to find the right way to start monit on my system.
My requirements are simple: start all services at boot time, stop
them when shutting down.
Using monit 4.10.1
The documentation recommends running monit from init. I find this
problematic as it lacks the flexibility of /etc/rc.d scripts to
the order of execution. I can choose to run monit before or after
scripts, but nowhere in between.
Is there any way around it ?
Assuming there isn't, I have a few issues with my /etc/init.d/
The FAQ includes a comment (suggested by myself...) to "start all"
of the init script.
Should this be called before or after starting the monit daemon ?
I tried both combination. In both I seem to run into situations
the time the second command runs, services haven't completed their
and the second command tries to restart the service.
I tried this with both "start all" and "monitor all", with similar
What's the clean solution ?
Perhaps to remove the state file and then start the daemon ? Will
that do it
? When monit starts, in the lack of a state file, does it assume
services are monitored and should be started ?
Thanks in advance