NTP time sever failing

[JP]

My ISY-99i is not sync'ing with the NTP server. I noticed it this morning when I checked to see if it had advanced to DST correctly (it didn't). When I hit the Sync Now button, I receive either a Java socket time exception error or a "request failed". The log shows a -60001 R/C. To get around the problem I just sync'ed with my PC.

 

Now I suspect that this is not happening all the time as the log only shows random errors over the last 30 days, it's just that the one day you really want it to work it didn't. I'm not not sure what the errors are telling me and if I need to do anything. BTW, I also sync'd several PCs manually with a different NTP server without problems to make sure it wasn't something network related. Is this a server issue maybe?

[MikeB]

Could be, you may want to try a different NTP server.

[rhughes]

I'm having the same problem today with a -60006 error in the log.

[Michel Kohanim]

Hello,

 

All NTP servers have mechanisms which prevent clients to query more frequently than some predefined periods. As such, please do make sure that your refresh interval is not less than 24 hours since, especially during heavily accessed times, the server will simply ignore your request.

 

Now, not adjusting to DST is a cause for concern. What versions of ISY firmware do you have? Adjusting for DST has NOTHING to do with the NTP server: ISY has to adjust the time automatically.

 

With kind regards,

Michel

 

I'm having the same problem today with a -60006 error in the log.

[rhughes]

I'm using v 2.7.0. When my ISY-99 didn't update for DST yesterday, I noticed that the time wouldn't synch using NTP, so I synched with the computer, which worked. I've tried 3 different servers: pool.ntp.org, 192.43.244.18 (NCAR) and time-b.nist.gov with no success. I'm pretty sure I verified this worked before, but it was a while ago.

[Michel Kohanim]

rhughes,

 

Thanks for the information. I am not at all worried about not being able to communicate with the NTP server (which is probably network related). What I am worried about is that your ISY didn't update for DST. This, if a bug, is a very serious one. Would you be kind enough to:

1. Make sure Day Light Saving box is checked

2. Manually adjust your ISY's time to 03.08.2009 01:59:50 AM

 

If all OK, ISY should automatically adjust to 3:00 AM when the clock reaches 2:00.

 

Please do let me know.

 

With kind regards,

Michel

 

I'm using v 2.7.0. When my ISY-99 didn't update for DST yesterday, I noticed that the time wouldn't synch using NTP, so I synched with the computer, which worked. I've tried 3 different servers: pool.ntp.org, 192.43.244.18 (NCAR) and time-b.nist.gov with no success. I'm pretty sure I verified this worked before, but it was a while ago.

[rhughes]

Hmmm. Well, that worked. I'm not sure what happened yesterday morning, but all seems fine now. I have an external app that I've developed that interacts with the ISY, so that may have caused some issues. I'll check it out more closely before I manually set the time if this happens again in the fall.

 

Since others aren't having problems with NTP, it must be my network. I'll work through that.

 

Thanks.

[JP]

I too have 2.7.0 and I have the default of once every 24 hours to check. I did play around with the default URL pool.ntp.org looking for a bad server but nothing conclusive though I agree with the suspicion. I will continue to test but I may take another day or two as I have another unrelated problem to deal with first (since the workaround worked).

[oberkc]

I, too have had continuous proplems synching to pool.ntp.org. (I was getting a red exclamation point on the configuration ta.) Until now I never spent many brain cells trying to figure that one out. I tried a couple more and found one that worked.

 

Coincidentally, the DST suddenly corrected itelf. Despite the Daylight Saving box checked, it did not update automatically. Once I found a working NTP site, however, the time now accounts for DST.

[JP]

Since the pool.ntp.org URL is a large pool of servers that can be changed at any time (yet changes may take 48 hours to update all caches), I'm assumming that I just hit a bad server that just happened to hit on worst day (I know 0.pool.ntp.org was bad that day and is OK now).

[f_richey]

Tried many different NTP locations, all come back with ISY error "Request Failed"

[aLf]

Just out of curiosity, give an example of how you are denoting the ntp server in ISY. I use the same one for ISY and many cameras and have never had a problem. It may simply be the address.

 

aLf

[f_richey]

right now it's pool.ntp.org, I tried others. it may be timing out too quickly under 2.7.0 ? Notification also does not work? All worked fine before upgrading to 2.7.0

[Michel Kohanim]

Hello f_richey,

 

Would you be kind enough to try an IP address instead of pool.ntp.org (on the DOS cmd prompt, type: nslookup pool.ntp.org). If this works, then it means that ISY cannot resolve names to IPs. This usually happens if your router ignores DNS requests OR if you have setup a static IP address with the wrong DNS.

 

With kind regards,

Michel

 

right now it's pool.ntp.org, I tried others. it may be timing out too quickly under 2.7.0 ? Notification also does not work? All worked fine before upgrading to 2.7.0

[f_richey]

Michel, That was the problem. I hard coded the IP address in the ISY and the DNS was not set. Once it was set properly, NTP works.

 

Thank You