Alerts generated when max_check_attempts set to 3

[Seth Simmons]

Yes you are.

If you have a host notification and set max_check_attempts to 1 and,
let's say you also have check_interval to 60 (1 min) for a host then
disconnect the cable, within the next minute Nagios check will fail and
send immediate notification of host down because the check attempt was
1.  If you say max_check_attempts is 3, and do the same thing, the host
will show as down, but unless you reconnect within the next couple min
before that 3rd check, Nagios won't send out a notification.  Once it
hits that 3rd check and is still in a down state, it will then send
notification of host down.  If by the 3rd check it has recovered, no
notification is sent.

HTH

-----Original Message-----
From: Deborah Martin [mailto:Deborah.Martin at Kognitio.com] 
Sent: Monday, November 24, 2008 6:08 AM
To: 'nagios-users at lists.sourceforge.net'
Subject: [Nagios-users] Alerts generated when max_check_attempts set to
3
Importance: High

Hi, 

Just a quick question - I'm changing the max_check_attempts from 1 to 3
for
a specific plugin and I wondered, does this mean that an email
notification
won't go out until the 3rd attempt is reached ? (Which is what I want to
achieve). Or will all 3 attempts generate an email notification. 

The docs say the following :- 

"max_check_attempts: This directive is used to define the number of
times
that Nagios will retry the service check command if it returns any state
other than an OK state. Setting this value to 1 will cause Nagios to
generate an alert without retrying the service check again. "

Am I understanding this correctly ? 

Thanks,
Deborah  



************************************************************************
***
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. 

Any unauthorised distribution or copying is strictly prohibited. 
Whilst Kognitio Limited takes steps to prevent the transmission of
viruses via e-mail, we can not guarantee that any email or attachment is
free from computer viruses and you are strongly advised to undertake
your own anti-virus precautions. 

Kognitio grants no warranties regarding performance, use or quality of
any e-mail or attachment and undertakes no liability for loss or damage,
howsoever caused. 

Kognitio Limited, a company registered in England and Wales. Registered
number 0212 7833. Registered Office:  3a Waterside Park, Cookham Road,
Bracknell, Berks, RG12 1RB. VAT number 864 4378 92.

Kognitio Inc, a company incorporated in Delaware, principal office 180
North Stetson, Suite 3500, Chicago, IL 60601, USA
************************************************************************
***

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when
reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null