Hi all, Today when I noticed a root nearly full I looked to see why Nagios hadn't flagged it. It was quickly apparent when I saw Nagios wasn't going to run the next service check until October of 2014!. I saw this for all services with the last check having been the same year. The system clock is definitely correct. Once I force a service check, the times in Nagios correct. Here is a sample service check before being forced to run. Any clue where to track this down? I've confirmed check intervals are sane. Thanks.
Current Status: OK (for ???) Status Information: HTTP OK HTTP/1.1 200 OK - 0.144 second response time Performance Data: time=0.143614s;;;0.000000 size=36569B;;;0 Current Attempt: 1/3 (HARD state) Last Check Time: 12-08-2014 13:54:37 Check Type: ACTIVE Check Latency / Duration: 0.221 / 0.160 seconds Next Scheduled Check: 12-08-2014 14:24:37 Last State Change: 12-01-2014 19:24:37 -- - Kyle --------------------------------------------- ky...@panix.com http://www.panix.com/~kylet --------------------------------------------- ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Nagios-users mailing list Nagios-users@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