Too many notifications / max_check_attempt useless

[Ian Chilton]

Hello,

> yes you're right but ... one may think that max_check_attempts works with the check_interval.
> For example, one would expect that if you set max_check_attemps to 5, nagios would check the host 5 times with a one minute interval betwen the checks (like it is for services). This is not the case.
> Here is an example log file:
> [22:05:23] HOST ALERT: fw-ns-msi;DOWN;HARD;3;FPING CRITICAL - 2.1.4.238 (loss=100.000000%, rta=0.000000 ms)
> [22:05:23] HOST ALERT: fw-ns-msi;DOWN;SOFT;2;FPING CRITICAL - 2.1.4.238 (loss=100.000000%, rta=0.000000 ms)
> [22:05:22] HOST ALERT: fw-ns-msi;DOWN;SOFT;1;FPING CRITICAL - 2.1.4.238 (loss=100.000000%, rta=0.000000 ms)
> As you can see all checks are execute immetiatly without any consideration for check_interval and interval_length


Check out:
http://nagios.sourceforge.net/docs/1_0/checkscheduling.html

You probably want to use: normal_check_interval and
retry_check_interval.


--ian



-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
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