[Top][All Lists]

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

Re: monit 4.3, what event for generic protocol failure?

From: Jan-Henrik Haukeland
Subject: Re: monit 4.3, what event for generic protocol failure?
Date: Tue, 18 May 2004 04:22:06 +0200
User-agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Reasonable Discussion, linux)

> "Tom O'Brien" <address@hidden> writes:
>> What is the event definition that triggers the alert?

Just to answer this one also, since that was your actual question :)
The event that triggers an alert if a connection fails or if a
protocol test fails is "connection". So when you correctly use:

 alert address@hidden { timeout connection checksum nonexist }
 alert address@hidden

you should get an alert when the protocol test fails, but remember
that monit only sends 1 (one) failed alert for each service and only
send a new failed alert if a service gets up and *then* fails
again. So when you did not get an alert it may be because the
connection to port 1033 failed earlier?

If this is not the case and you didn't not get an alert the first time
your send/expect test failed it's a bug in monit and we need to fix
it. However, doing a fast test I can't really reproduce the problem on
my machine.

Jan-Henrik Haukeland

reply via email to

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