Problem with "retry check interval"

[Alexander Schaefer]

I think, i should distinguish between service_check_interval and
host_check_interval, The last one will be executed on demand by nagios, but the
unclear is; "Where can i define the host retry_check_interval" ?


> But i can not understand why, the particular host X1_voicegate "retry check
> interval" works with check delay of only 3 seconds??? This information i can
> see in Nagios event log:
>
>  [09-06-2004 13:46:12] HOST ALERT: X1_voicegate;DOWN;HARD;3;PING CRITICAL -
> Host Unreachable (10.4.11.13)
> [09-06-2004 13:46:09] HOST ALERT: X1_voicegate;DOWN;SOFT;2;PING CRITICAL -
Host
> Unreachable (10.4.11.13)
> [09-06-2004 13:46:06] HOST ALERT: X1_voicegate;DOWN;SOFT;1;PING CRITICAL -
Host
> Unreachable (10.4.11.13)
>
>
> It is a bug in nagios or there is another invisible configuration
posibilities
> in nagios?
>
> Thanks for you ideas
>
> Alex
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> 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 BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
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