<div>Hi, Marc.</div> <div> </div> <div>Thank you for your answer.</div> <div> </div> <div>Do you think that just after a "HARD UP" the check number should be reset to "1"?</div> <div> </div> <div>I don´t think so. Look at other messages log, for the same host:</div> <div> </div> <div> </div> <div>[1236260301] HOST ALERT: sani6as05;DOWN;SOFT;1;Network is unreachable<br>[1236260361] HOST ALERT: sani6as05;UP;SOFT;2;TCP OK - 0.538 second response time on port 135<br>[1236260681] HOST ALERT: sani6as05;DOWN;SOFT;1;Network is unreachable<br> [1236260751] HOST ALERT: sani6as05;DOWN;SOFT;2;Network is unreachable<br>[1236260821] HOST ALERT: sani6as05;DOWN;SOFT;3;Network is unreachable<br>[1236260891] HOST ALERT: sani6as05;DOWN;HARD;4;Network is unreachable<br></div> <div>In this example, after the "UP;SOFT;2" we had a "DOWN;SOFT;1".</div> <div><br>That is my doubt? Someties Nagios resets the check number, sometimes it doesn´t.</div> <div> </div> <div>Thank you again.</div> <div>Rodney.<br></div> <div class="gmail_quote">On Thu, Mar 5, 2009 at 12:22 PM, Marc Powell <span dir="ltr"><<a href="mailto:marc@ena.com">marc@ena.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div class="im"><br>On Mar 5, 2009, at 8:53 AM, Rodney Ramos wrote:<br><br>> I´m noticing that, sometimes, the check attempt number do not reset<br>> to "1" after a recovery state, as we can see below:<br> ><br>> [1236254782] HOST ALERT: sani6as05;DOWN;SOFT;1;No route to host<br>> [1236254852] HOST ALERT: sani6as05;UP;SOFT;2;TCP OK - 0.519 second<br>> response time on port 135<br><br></div>^^^^^ Wasn't in a HARD OK state yet so hadn't _really_ recovered.<br> <div class="im"><br>> [1236255172] HOST ALERT: sani6as05;DOWN;SOFT;2;CRITICAL - Socket<br>> timeout after 10 seconds <---- Should be "SOFT:1", not "SOFT:2"<br>> [1236255242] HOST ALERT: sani6as05;DOWN;SOFT;3;Network is unreachable<br> > [1236255312] HOST ALERT: sani6as05;DOWN;HARD;4;Network is unreachable<br>><br>> Is this a normal behaviour or is it a Nagios problem?<br><br></div>Doesn't appear to be a bug, IMHO.<br><br>--<br>Marc<br><br> <br>------------------------------------------------------------------------------<br>Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA<br>-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise<br> -Strategies to boost innovation and cut costs with open source participation<br>-Receive a $600 discount off the registration fee with the source code: SFAD<br><a href="http://p.sf.net/sfu/XcvMzF8H" target="_blank">http://p.sf.net/sfu/XcvMzF8H</a><br> _______________________________________________<br>Nagios-users mailing list<br><a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br><a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<br>::: Messages without supporting info will risk being sent to /dev/null<br></blockquote></div><br>