Nagios Bug: use_agressive_host_checking not in nagios.cfg makes host alerts fail

[Quanah Gibson-Mount]

After pulling down the default configs, and comparing my nagios.cfg with 
its nagios.cfg, I started adding in various things that weren't in the 
nagios.cfg we deploy because the documentation states they have default 
values.

At some point, host down alerts started working as expected, so I backed 
out the changes until they stopped working again.

This occurred at the point at which I removed the 
"use_aggressive_host_checking=0" line (My email client will not let me 
spell it the incorrect way it is spelled in Nagios :P ).

According to the Nagios documentation, this parameter is supposed to be 
defaulted to 0:

<http://nagios.sourceforge.net/docs/1_0/configmain.html#use_aggressive_host_checking>

(Damn, even the link is wrong because my email client is throwing in the 
extra g to make it spelled correctly).

So there is a bug in that logic somewhere.

obsess_over_services

does not exhibit similar behavior with services, since I didn't have that 
defined either, and service alerts were never an issue.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
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