[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[monit] state file persistence

From: Nick Upson
Subject: [monit] state file persistence
Date: Tue, 24 Feb 2009 13:57:35 +0000

I appear to have a situation where sometimes (as usual :) ) after a
reboot monit shows all processes as unmonitored and they just stay
that way - this is my big problem, also sometimes they are all shown
as unmonitored but they they change to initialising etc.

this is monit 4.10, What is the way to stop monit normally (see below)
when it's run via inittab

I found these quotes:

"the state file is used just in case that monit was either reloaded
(for example using "monit reload" or SIGHUP) or crashed and was
started again to recover last state. If monit is stopped normally, the
state file is not used on next start (it's unlinked/deleted on stop).

To test the state persistence, you can try "monit reload" or kill -9
monit and start monit ... the state including monitoring mode should
recover. "

and, in answer to a request for the state to survive a reboot
"The state was changed to be persistent even across monit restarts, it
will be part of next monit release.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]