"host" check Not firing as expected


#1

All,

I’m coming from Nagios 1.x; and trying to port our config to nagios 3.2.3. It seems that whether I go forward, or backward revisions (3.x) the problem still exists, so i’m certain the issue is the config.

I understand the whole “host checks dont fire unless a service has issues”, and i"m cool with that.

Our nagios 1.x is configured to check_ping 10 times before it alerts us. We can see in the log that this happens about every 10 seconds, and then it will (properly alert) in about 1:00 to 1:30 (depending on when it saw the service die).

Nagios 3.x; however, takes FOREVER to get thru 10 hostchecks. It seems to do the first 2 fairly quickly (still - 40 seconds apart) and then a while for the rest. The command line being run is exactly the same; as well as the host template:

Nagios3x:
define host {
name generic-host
register 0
max_check_attempts 10
notification_interval 120
notification_period 24x7
notification_options d,r
notifications_enabled 1
check_command check-host-alive
event_handler_enabled 1
flap_detection_enabled 1
process_perf_data 1
retain_status_information 1
retain_nonstatus_information 1
}

define host {
use generic-host
host_name TESTHOST.local
alias TESTHOST
address testhost.local
}

Nagios 1.x
define host {
name generic-host
register 0
max_check_attempts 10
notification_interval 120
notification_period 24x7
notification_options d,r
notifications_enabled 1
check_command check-host-alive
event_handler_enabled 1
flap_detection_enabled 1
process_perf_data 1
retain_status_information 1
retain_nonstatus_information 1
}

define host {
use generic-host
host_name TESTHOST.local
alias TESTHOST
address testhost.local
}