no max check attempts for host checking?

[Emanuel Massano]

Frost, Mark {PBG} wrote:
> 
>> -----Original Message-----
>> From: nagios-users-bounces at lists.sourceforge.net 
>> [mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf 
>> Of Thomas Guyot-Sionnest
>> Sent: Wednesday, May 14, 2008 10:37 PM
>> To: Mark Frost
>> Cc: nagios-users at lists.sourceforge.net
>> Subject: Re: [Nagios-users] no max check attempts for host checking?
>>
>> -----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
> 
> Hmmm.  I'm actually running Nagios 3.0.2 (sorry forgot to mention that).
> 
> The central server has host checking disabled, but allows passive
> checks.  The distributed node is configured for active checks (of
> course) and obsessing.  The host configuration on the distributed node
> lists the max_check_attempts as 10.
> 

Hi,

I had the same problem and reported the bug to nagios-devel. The problem 
is in the orphan host checks.
In the changelog for v3.0.3 it seems it has been fixed :) Thanks!!
So just try the new nagios version!

Cheers,
Emanuel Massano


> Mark
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> 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

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
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