It seems that retry interval in my configuration for host checks is not
working.
I'm using Nagios3rc2.

Here is definition of host:

define host{
        host_name                               malm.proxy.xxx.xxx
        alias                           malm
        address                         195.xxx.xxx.xxx
        hostgroups                      PROXY
        check_command                   check_host_alive
        max_check_attempts                      3
        check_interval                  5
        retry_interval                  5
        check_period                    24x7
        process_perf_data                       1
        contact_groups                  admins, duty
        notification_interval           10
        notification_period             24x7
        notification_options            d,u,r
}

But when i disable icmp on that hosts, so host is unreachable via icmp, in
log file is this:

[1204015545] HOST ALERT: malm.proxy.verza.net;DOWN;SOFT;1;PING CRITICAL -
Packet loss = 100%
[1204015565] HOST ALERT: malm.proxy.verza.net;DOWN;SOFT;2;PING CRITICAL -
Packet loss = 100%
[1204015615] HOST ALERT: malm.proxy.verza.net;DOWN;HARD;3;PING CRITICAL -
Packet loss = 100%

So delay between first and 2nd check is 20 secs and between 2nd and 3rd is
50secs, but i expected it to be 5 minutes in both cases since retry_interval
is setup to 5 (and interval length is 60).
There are defined about 5 services on that host. But i think that service
checks should be suppressed until host it up again.
Is this some bug or i have some missconfiguration there ?


Thx,
    DD



-------------------------------------------------------------------------
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@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

Reply via email to