Nagios host check retry interval inconsistent

[Yu Watanabe]

>Not that it fails to reschedule it. Just that failing service checks always
>force a hostcheck to occur. That's by design. The change was, afair, to
>make sure Nagios doesn't reschedule the hostcheck when a forced hostcheck
>happens, and also to not increment the check attempt variable.

  Sorry my words were wrong. I meant by the interval is not the value that 
  I have specified. If I list both host check and service check, it
  would be like this:

[1289460901] SERVICE ALERT: localhost;icmp_ping;CRITICAL;SOFT;1;CRITICAL - Network Unreachable (192.1.1.1)
[1289460911] HOST ALERT: localhost;DOWN;SOFT;1;CRITICAL - 192.1.1.1: rta nan, lost 100%
[1289460931] SERVICE ALERT: localhost;icmp_ping;CRITICAL;HARD;1;CRITICAL - Network Unreachable (192.1.1.1)
[1289460951] HOST ALERT: localhost;DOWN;SOFT;2;CRITICAL - 192.1.1.1: rta nan, lost 100%
[1289460991] HOST ALERT: localhost;DOWN;SOFT;3;CRITICAL - 192.1.1.1: rta nan, lost 100% 
[1289461011] HOST ALERT: localhost;DOWN;SOFT;4;CRITICAL - 192.1.1.1: rta nan, lost 100%
[1289461032] HOST ALERT: localhost;DOWN;SOFT;5;CRITICAL - 192.1.1.1: rta nan, lost 100%
[1289461071] HOST ALERT: localhost;DOWN;SOFT;6;CRITICAL - 192.1.1.1: rta nan, lost 100%
[1289461101] HOST ALERT: localhost;DOWN;SOFT;7;CRITICAL - 192.1.1.1: rta nan, lost 100%
[1289461111] HOST ALERT: localhost;DOWN;SOFT;8;CRITICAL - 192.1.1.1: rta nan, lost 100%
[1289461151] HOST ALERT: localhost;DOWN;SOFT;9;CRITICAL - 192.1.1.1: rta nan, lost 100%
[1289461191] HOST ALERT: localhost;DOWN;HARD;10;CRITICAL - 192.1.1.1: rta nan, lost 100%

  However, when it comes to the 4th host check , the host check occured only in 20 seconds
  not 40 seconds. I see that service check already turned to HARD status ,so I just
  don't see the reason why the interval suddenly changed to 20 seconds.

Any idea about this?

Thanks!
Yu Watanabe

Andreas Ericsson さんは書きました:
>On 11/11/2010 12:21 PM, Yu Watanabe wrote:
>> Hello Andreas.
>> 
>> Thank you for the reply.
>> 
>>> Failing service checks trigger host checks. I think there was some
>>> patch to make forced hostchecks not count as an attempt. I might
>>> be mistaken though, but if you upgrade your Nagios you should see
>>> it behave differently.
>> 
>>    So in old version there are some incosistency for the host check retry?
>>    Such as Nagios fails to reschedule according to the host check retry.
>> 
>
>Not that it fails to reschedule it. Just that failing service checks always
>force a hostcheck to occur. That's by design. The change was, afair, to
>make sure Nagios doesn't reschedule the hostcheck when a forced hostcheck
>happens, and also to not increment the check attempt variable.
>
>I could be entirely wrong though.
>
>>    I am very curious about this and if there were a discussion preriously,
>>    do you have a reference about that discussion? Else, I will try to check the
>>    source code.
>> 
>
>Google and a decent source code editor are your best bets. Good luck.
>
>-- 
>Andreas Ericsson                   andreas.ericsson at op5.se
>OP5 AB                             www.op5.se
>Tel: +46 8-230225                  Fax: +46 8-230231
>
>Considering the successes of the wars on alcohol, poverty, drugs and
>terror, I think we should give some serious thought to declaring war
>on peace.
>


------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
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