The timer of "Last State Change" wrong

[Thanh vovinam]

Hello Nagios users,

We are using Nagios 3.0rc2 to monitor many machines (passiv, activ,
-cheks).
We have one Nagios server (master) and 5 Nagios server (slaver).
Nagios Slaver  monitors  many machines (hosts) and  forwards  events  to
Nagios Master (about 8.000 passiv checks).
Last few days ago occured some "strange" on some hosts on Nagios server
Master (other hosts work OK). Look "Service State Information" from one of
"stranged" hosts following:
You can see:
Last State Change from host was changed "suddenly" 2 months early.
What happens? Can you help us? How can we change the timer of "Last State
Change" bak to current timer?

..................

*Service State Information*
Current Status:
OK   (for ???)

Status Information:DISK OK - free space: /data 61546 MB (32%
inode=97%): Performance
Data:/data=125239MB;157424;177102;0;196781 Current Attempt:1/4  (HARD
state) Last
Check Time:2008-05-21 11:54:10 Check Type:PASSIVE Check Latency /
Duration:N/A / 0.000
seconds Next Scheduled Check:  N/A Last State Change:2008-07-22 02:56:38 Last
Notification:N/A (notification 0) Is This Service Flapping?N/A In Scheduled
Downtime?  NO
Last Update:2008-05-21 11:54:52  ( 0d 0h 0m 4s ago)

Thanks,

Best Regards,

Thanh Ngoc Tran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080521/d12b3df6/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- 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