-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Martin Pala
Sent: Tuesday, November 18, 2008 1:17 PM
To: This is the general mailing list for monit
Subject: Re: [monit] monit not monitoring
"monit stop all" will really stop the services and set the monitoring
mode to unmonitored. If the server will be powered-off uncleanly and
the monit state file won't be unlinked, then the "unmonitored"
monitoring mode will be restored on next Monit start. The next monit
release (monit-5.0) keeps the state file in fact now so the monitoring
mode is persistent across monit restarts. In such case it will be
necessary to perform "monit start all" to enable the services
monitoring.
Martin
On Nov 18, 2008, at 9:07 PM, Gilad Benjamini wrote:
1. Standard pid configuration; check process XX with pidfile /var/
run/XX.pid
3. No
5. 4.10.1
About question #2: I suspect that this might be related to the
problem
I am not sure what the right terminology is, so I'll explain things
in my
own words.
I start monit from an /etc/init.d script. The configuration file
includes
the two files from /etc/monit.d, realizes that the pid file
represents a
dead process, and starts it.
As recommended in the monit faq, I added 'monit stop all' before
stopping
monit. A different place in the documentation leads me believe that
stopping
a service turns it into an un-monitored service. Combine that with
the fact
that some of my machines might have been powered off abruptly, and
it might
be that monit somehow stuck in this situation.
Does this make any sense ?
If that's the case, I think I should modify that monit /etc/init.d
script,
to run "monit start all" after monit starts.
Does THIS make sense ?
TIA
Gilad
-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Martin Pala
Sent: Tuesday, November 18, 2008 11:27 AM
To: This is the general mailing list for monit
Subject: Re: [monit] monit not monitoring
There's too little informations provided to say what's the root
cause.
1.) What's the configuration of these services?
2.) Are they monitored automatically or do you use manual monitring
mode?
3.) Do you use any timeout or unmonitor statement on excessive
number
of errors?
4.) Please also run monit in verbose mode (-v option) and check
logs.
5.) What Monit version it is?
Thanks,
Martin
On Nov 18, 2008, at 9:09 AM, Gilad Benjamini wrote:
I am using monit to monitor two applications with pid files.
During stress tests, I start up 25 machines, all running the same
image.
They differ in a few not-monit-related configuration files, such as
IP
address and security identity.
On 3-5 of the machines, the applications simply don't start.
/var/log/messages shows "Monit has not changed" and nothing else.
monit status shows me both applications as not monitored.
Any ideas how to even start investigating this ?
--
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
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general