[Top][All Lists]

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

Re: [monit] Passive Mode question

From: Martin Pala
Subject: Re: [monit] Passive Mode question
Date: Sat, 24 Oct 2009 19:34:13 +0200


the only change in 5.x was, that the state file is persistent across restarts (formerly it was removed on Monit stop). The monitoring mode is restored from the statefile, which could cause the problem in your case (i was not able to reproduce the problem).

To solve the issue it should help to:
1.) stop Monit
2.) remove statefile (by default in home of user under which Monit is running: ~/.monit.state, can be customized with 'set statefile ...' statement).
3.) start Monit

In next release (Monit 5.1) we'll remove the recovery of monitoring mode from statefile as it is no longer needed anyway.


On Oct 20, 2009, at 8:30 PM, Nelson Vale wrote:


I've been using monit v.4.7 for a while without any problems, and now I decided to upgrade to the most recent version. So I've made some tests with my 4.7 configuration and everything seems to work fine with the exception of the "mode passive". When monit monitors a service that is in this mode if the service is stopped it will start it the same. I've tried this with different versions (5.0.3, 5.0.2, 5.0.1 and 4.10) and they all have the same problem. With 4.7 this works just fine.

One of the files that I'm using is this one:

check process slapd with pidfile /var/run/
    start program = "/etc/init.d/ldap start"
    stop program = "/etc/init.d/ldap stop"

    mode passive

    if failed host port 389 protocol ldap3 then restart
    if cpu usage is greater than 70 percent for 2 cycles then alert
    if cpu usage > 90% for 5 cycles then restart
    if 5 restarts within 5 cycles then timeout

Has the "mode" feature changed anyway since 4.7?


Nelson Vale
To unsubscribe:

reply via email to

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