My ISY decided to time travel last night for some unexplained reason. I noticed this morning that some timed events had not occurred and saw two interesting things in the console:

 

- System time was about 8am on 8/16/1941

 

- last start/end times in program summary were all 9/20/1977 or 9/21/1977

 

Hmmm. First step: "Synchronize Now" to reset time. This worked fine. System time is correct, as are "next run" times in program summary.

 

Next: downloaded log and saw the following two entries of interest:

 

0 CLI-WBu Wed 09/02/2009 05:11:59 PM System -140002

[Hall C] DR light Status 100% Fri 08/15/1941 01:02:44 PM System Log

 

So the time decided to reset itself some time after 5:11pm yesterday, leaving no trace in the log. Any ideas? My ntp server is configured to pool.ntp.org, and syncs every 24 hours. But it seems hard to believe that the time could change this drastically via an NTP update.

 

Thanks,

--Mark

Hi Mark,

 

Did you recently upgrade the firmware?

 

I have seen this myself several times when changing firmware. Each time clearing the java cache set things right.

 

Rand

Hi Rand,

 

Last time I updated firmware was end of July, to 2.7.6. So no recent change in that department.

 

Interesting about possible java cache interaction. But that seems unlikely in this case since the time obviously was reset when no admin client was connected to the ISY. Right? At any rate, simply syncing the time was all it took to fix it for me.

 

This is one of those things I'm not going to lose sleep over unless it happens again. But it was curious enough to bring up in the forum!

 

--Mark

Hi markens,

 

There are two explanations:

1. The NTP server returned a bogus time

2. The RTC is going bad

 

Please do keep an eye and let us know if it happens again.

 

With kind regards,

Michel

Please do keep an eye and let us know if it happens again.

Will do. Thanks,

 

--Mark