BUG: Passive host check results are always in HARD state.

[Ethan Galstad]

jan.david at agfa.com wrote:
> 
> Hi,
> 
> We have a distributed Nagios set-up with three (slave) check engines 
> performing active checks and sending their results to a master server 
> which collects all results and sends out alarms if need be.
> 
> Our department had a lot of complaints regarding remote hosts connected 
> over a WAN link that give out a lot of false positives.
> 
> Because  WAN links are more prone to packet loss than LAN links, we've 
> set the number of host retries to 10, figuring that this would avoid any 
> false alerts about hosts being down while in fact it is just a temporary 
> glitch in the line.
> 
> This setup did not work however. Further investigation about the cause 
> revealed what I believe to be a bug.
> 
> */While receiving host check results in PASSIVE mode, the number of 
> retries is not taken into account and a negative response will 
> immediately results in a HARD state, which in turn sends out alerts./*
> 
[snip]
> 
> Note that PASSIVE services checks work as expected, it's only host 
> checks that exhibit this behaviour.
> 
> Would it be possible to post a patch for this bug or could a fix be 
> incoporated in a next release?
> 
> Best Regards,
> 
> Jan David
> 

This is a feature, rather than a bug, but the behavior is undesireable. 
  The host check logic has changed in the 3.0 development code and 
passive checks no longer result in HARD-only states.


Ethan Galstad,
Nagios Developer
---
Email: nagios at nagios.org
Website: http://www.nagios.org

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642