The monitoring mode will be most probably restored from state file ... please try:
1.) stop monit 2.) remove the statefile 3.) start monit
Default state file location is ~/.monit.state (can be customized with "set statefile ...")
Martin
On Sep 15, 2009, at 5:52 PM, Frank wrote: Around 50 times yes./.. Tried all, restart service , stop monitoring, start monitoring, monit start all , etc Tried to look into source to see what it based it on no luck From: address@hidden [mailto:address@hidden On Behalf Of Martin Pala
Sent: September-15-09 2:38 AM
To: This is the general mailing list for monit
Subject: Re: [monit] monit and active/passive Have you tried to reload monit?: On Sep 14, 2009, at 11:30 PM, Frank wrote:
Full config is first thread... but here it is again set logfile /var/log/monit.log set eventqueue basedir /var/monit/ slots 1000 #following line has been rewritten for the list ;) check process freeswitch with pidfile "/usr/local/freeswitch/log/freeswitch.pid" start program "/usr/bin/screen -d -m /usr/local/freeswitch/bin/freeswitch" #start program "/usr/bin/screen -S freeswitch -d -m /usr/local/freeswitch/bin/freeswitch -nf" stop program "/usr/local/freeswitch/bin/freeswitch -stop" if totalmem > 140.0 MB then alert if totalmem > 180.0 MB for 3 cycles then restart # Checks sip port on localhost, not always suitable # if failed port 5060 type UDP then restart # Checks mod_event_socket on localhost. Maybe more suitable #if failed port 8021 type TCP then restart if 5 restarts within 5 cycles then timeout From: address@hidden [mailto:address@hidden] On Behalf Of Martin Pala
Sent: September-14-09 1:35 AM
To: This is the general mailing list for monit
Subject: Re: [monit] monit and active/passive It seems that the configuration has changed probably on the passive host (?). You can try to reload the configuration: If this won't help, can you send the full configuration file from the passive host? On Sep 13, 2009, at 11:00 PM, Frank wrote: Monitoring status monitored The dump doesn’t show anything about active/passive Use process engine = True Poll time = 60 seconds with start delay 0 seconds Expect buffer = 256 bytes Event queue = base directory /var/monit/ with 1000 slots On the working one it says..: Monitoring status monitored From: address@hidden [mailto:address@hidden] On Behalf Of Martin Pala
Sent: September-13-09 4:47 PM
To: This is the general mailing list for monit
Subject: Re: [monit] monit and active/passive can you run monit like this and check output?: monit -vIc <pathtomonitconfiguration> It will dump parsed configuration on the beginning. The passive mode means, that the service is monitored, but not restarted ... are you sure it is in passive mode? Isn't it just unmonitored? On Sep 13, 2009, at 9:32 PM, Frank wrote: I have 2 exactly same monitrc files.. One is active other stays stuck in passive mode... set logfile /var/log/monit.log set eventqueue basedir /var/monit/ slots 1000 #following line has been rewritten for the list ;) check process freeswitch with pidfile "/usr/local/freeswitch/log/freeswitch.pid" start program "/usr/bin/screen -d -m /usr/local/freeswitch/bin/freeswitch" #start program "/usr/bin/screen -S freeswitch -d -m /usr/local/freeswitch/bin/freeswitch -nf" stop program "/usr/local/freeswitch/bin/freeswitch -stop" if totalmem > 140.0 MB then alert if totalmem > 180.0 MB for 3 cycles then restart # Checks sip port on localhost, not always suitable # if failed port 5060 type UDP then restart # Checks mod_event_socket on localhost. Maybe more suitable #if failed port 8021 type TCP then restart if 5 restarts within 5 cycles then timeout -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general
|