It seems that the configuration has changed probably on the passive
host (?). You can try to reload the configuration:
monit reload
If this won't help, can you send the full configuration file from the
passive host?
Thanks,
Martin
On Sep 13, 2009, at 11:00 PM, Frank wrote:
Monit/t says...
Status running
Monitoring mode passive
Monitoring status monitored
The dump doesn’t show anything about active/passive
Log = True
Use syslog = False
Is Daemon = True
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
Monitoring mode = active
On the working one it says..:
Status running
Mode active
Monitoring status monitored
They run same versions
From: [email protected] [mailto:[email protected]
] 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
Hi,
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?
Thanks,
Martin
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...
Any idea why ?
set daemon 60
set logfile /var/log/monit.log
set mailserver myemaildomain.com
set httpd port 9999
allow 0.0.0.0
allow 127.0.0.1
set eventqueue basedir /var/monit/ slots 1000
#following line has been rewritten for the list ;)
set mmonit http://user:p...@host:myport/collector
# Freeswitch
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
alert em...@mydomain
mode active
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
