Ok here's the problem, my Nagios installation (4.3.2) passive host check seemed to be ignoring the check_interval directive. There's some hosts behind firewall, so passive check comes into action. These passive hosts submit passive check via NCPA to my Nagios NRDP server. It works great when the host's up, but when the passive host goes down, it took sometime to go into critical hard state!
Here's my config for passive-host, where check_interval is set to run minutely. The intention is the make the passive host go down (hard state) asap in order to suppress the host's services' notification.
Code: Select all
define host{
name passive-host
use generic-host
active_checks_enabled 0
passive_checks_enabled 1
check_interval 1
max_check_attempts 1
freshness_threshold 120
check_command check_dummy!2!"Host is stale"
register 0
}
Code: Select all
root@jp-1:/usr/local/nagios/var# grep "puppetmas" nagios.debug | grep "Host Che"
[1509796693.001547] [008.0] [pid=593] ** Host Check Event ==> Host: 'puppetmaster.somedomain.com', Options: 3, Latency: 1.000070 sec
[1509796933.008809] [008.0] [pid=593] ** Host Check Event ==> Host: 'puppetmaster.somedomain.com', Options: 3, Latency: 0.000535 sec
[1509797173.001135] [008.0] [pid=593] ** Host Check Event ==> Host: 'puppetmaster.somedomain.com', Options: 3, Latency: 1.000068 sec