On Mar 5, 2009, at 8:53 AM, Rodney Ramos wrote: > I´m noticing that, sometimes, the check attempt number do not reset > to "1" after a recovery state, as we can see below: > > [1236254782] HOST ALERT: sani6as05;DOWN;SOFT;1;No route to host > [1236254852] HOST ALERT: sani6as05;UP;SOFT;2;TCP OK - 0.519 second > response time on port 135
^^^^^ Wasn't in a HARD OK state yet so hadn't _really_ recovered. > [1236255172] HOST ALERT: sani6as05;DOWN;SOFT;2;CRITICAL - Socket > timeout after 10 seconds <---- Should be "SOFT:1", not "SOFT:2" > [1236255242] HOST ALERT: sani6as05;DOWN;SOFT;3;Network is unreachable > [1236255312] HOST ALERT: sani6as05;DOWN;HARD;4;Network is unreachable > > Is this a normal behaviour or is it a Nagios problem? Doesn't appear to be a bug, IMHO. -- Marc ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Nagios-users mailing list [email protected] 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
