Last Check Time Issue

[Calhoun, Matthew]

This is running Nagios 3.0.5 on RHEL 5.

Thanks,
Matt

From: Calhoun, Matthew [mailto:mcalhoun at iodatacenters.com]
Sent: Friday, December 12, 2008 10:08 AM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] Last Check Time Issue

All:

We have about 1500 services that are being passively checked (custom scripts that write to the external command file). We've noticed an issue where the "Last Check" time for the service is many hours behind, but the "Last Update" time is correct and the service is alarming, etc. properly. Does anyone have an idea as to why the Last Check Time isn't being updated properly?

Thanks,
Matt

Current Status:   OK   (for 4d 22h 25m 13s)
Status Information: OK: No Alarms Present
Performance Data:
Current Attempt: 1/1  (HARD state)
Last Check Time: 12-12-2008 04:20:12
Check Type: PASSIVE
Check Latency / Duration: N/A / 0.000 seconds
Next Scheduled Check:   N/A
Last State Change: 12-07-2008 11:33:00
Last Notification: N/A (notification 0)
Is This Service Flapping? N/A
In Scheduled Downtime?   NO
Last Update: 12-12-2008 09:57:59  ( 0d 0h 0m 14s ago)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20081212/1272be7c/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
-------------- 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