reload appears to cause force of DOWN; SOFT; x to DOWN; HARD; 1

[Sean McKell]

Running 3.4.1:
I see this strange anomaly, where a host check is in the middle of doing 
retries before hitting max_attempts, but after a server reload occurs, the 
next check is automatically forced to DOWN;HARD;1, as seen here:

[2013-06-04 08:40:21] HOST ALERT: 5gt4;DOWN;SOFT;1;CRITICAL: Connection 
timed out to '' after 160 seconds (user 'chk'). Expected prompt not found. 
Last output was ''.
[2013-06-04 08:47:18] HOST ALERT: 5gt4;DOWN;SOFT;2;CRITICAL: Connection 
timed out to '' after 160 seconds (user 'chk'). Expected prompt not found. 
Last output was ''.
[2013-06-04 08:54:03] HOST ALERT: 5gt4;DOWN;SOFT;3;CRITICAL: Connection 
timed out to '' after 160 seconds (user 'chk'). Expected prompt not found. 
Last output was ''.
(reload happens here)
[2013-06-04 09:00:52] HOST ALERT: 5gt4;DOWN;HARD;1;CRITICAL: Connection 
timed out to '' after 160 seconds (user 'chk'). Expected prompt not found. 
Last output was ''.

Why is it skipping the rest of the attempts and going straight to 
DOWN;HARD after the reload ?
Seems like a bug to me.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20130613/17cc06cc/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
-------------- next part --------------
_______________________________________________
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