RE: Monit displays "not monitored" for services it fails to start - [NEWSENDER] Message is from an unknown sender

[Qi Lu]

Hi Martin and Marcus,

Thank you very much for quick reply. Yes, that is what I mean. I used 'if 3 
restarts within 5 cycles then timeout'. Within first 3 cycles, if Monit fails 
to start application, it displays 'Execution failed', after 3 tries, it 
displays "not monitored".
Because there is no people monitor the console all the time, it is helpful to 
display either 'failed to restart' or 'timeout' to distinguish intending not 
monitor, especially for different administrators.

Qi

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Marcus Mülbüsch
Sent: Thursday, February 01, 2007 8:10 AM
To: This is the general mailing list for monit
Subject: Re: Monit displays "not monitored" for services it fails to start - 
[NEWSENDER] Message is from an unknown sender

Martin Pala schrieb:

> Maybe you meant that when you used 'if <x> restarts within <y> cycles 
> then timeout' rule then monit sets the state to 'not monitored' when the 
> rule is true?

If that it was he meant I second that request.

While I realize that I ordered monit to no longer monitor the services, 
in reality there is a difference.

When I type "monit unmonitor service" or click the button on the web 
interface it is a "unmonitored by user request".

When monit no longer monitors a service because the config file told it 
to do so it is a "unmonitored by timeout".

To show different texts in the Web interface (or with "monit summary" 
would indeed be helpful.

Marcus


--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general