Weird failure-to-count error

[Steven Schwartz]

I have a test (proprietary internal test) that runs, reports critical (not surprising, as it's doing a web submit to a non-running webserver), which then fails again every 15 minutes; and never moves from "Current Attempt: 1/3", and therefore does not notify.

Interestingly enough, the subsequent failures do not log; the only way I was able to tell that, in fact, they had failed was checking the "Last Check Time" and "Next Scheduled Active Check" and seeing them advance, while the "Current Attempt" remained stable.

The "Current State Duration" is updated correctly, but it still does not page.

Has anyone seen a problem like this before, and if so, what did you do to fix it?

Steven Schwartz
Unix Systems Administrator,
Gracenote, Inc.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20110117/42c744fd/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
-------------- 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