no max check attempts for host checking?

[Thomas Guyot-Sionnest]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/05/08 12:46 PM, Mark Frost wrote:
> Hello.  I have something that's not working the way I'd expect.
> 
> We are monitoring services on windows hosts and as is common practice,
> not explicitly checking the host state.  Wehn the host gets rebooted, I
> expect that a service might fail, then Nagios would attempt a host
> check.  I would like the host check to not alert on a single ping
> failure, but rather hold off for say 5 failures before it sends an
> alert.  The intent is to not get an alert if the box is just being 
> rebooted.
> 
> I've set the following for my test host:
> 
> max_check_attempts 10
> check_interval 0
> retry_interval 1
> active_checks_enabled no
> 
> 
> Our configuration is a distributed one so the distributed node has
> obsession turned on, but the central node does not.
> 
> When testing, we find that no matter what I set the max_check_attempts
> to, an alert is sent on the first ping failure.
> 
> Is there something I'm missing?

No. Nagios 2.0 always treat passive host checks as HARD.

Here's the answer from Ethan about this:

http://osdir.com/ml/network.nagios.devel/2006-07/msg00009.html

Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIK6HP6dZ+Kt5BchYRAjYXAJ9taoWEpXlRCO0+P/QTWguQNNQj1QCfSuou
Za9UNSmJsONr+DcWmp7+Osg=
=1SSx
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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