M1 time 2 days late?

[fleetz]

Using ntp2.tpg.com.au as the NTP time server site on a friends M1 system. They had an alarm event and ask me what was the issue was, on checking the log the date is out exactly 2 days. That wasn't the alarm event problem of course, sorted that out and in doing so noticed the date discrepency.

I use the same ntp2.tpg.com.au NTP site on mine and I have checked time and date and all is good. I connected my friends M1 (XEP) to RP2 and tested the time server connection and it came back passed and the time had been up dated by the server but the date is still 2 day out.

I test mine and it confirms that it passed and updated the clock and is the correct time day date?

Any clues?

What timers are you guys using? I would like to find a confirmed working time server site so I am at least going from a reference site.

Thanks and regards,

Fleetz

 

[wuench]

Using ntp2.tpg.com.au as the NTP time server site on a friends M1 system. They had an alarm event and ask me what was the issue was, on checking the log the date is out exactly 2 days. That wasn't the alarm event problem of course, sorted that out and in doing so noticed the date discrepency.

I use the same ntp2.tpg.com.au NTP site on mine and I have checked time and date and all is good. I connected my friends M1 (XEP) to RP2 and tested the time server connection and it came back passed and the time had been up dated by the server but the date is still 2 day out.

I test mine and it confirms that it passed and updated the clock and is the correct time day date?

Any clues?

What timers are you guys using? I would like to find a confirmed working time server site so I am at least going from a reference site.

Thanks and regards,

Fleetz

Sometimes an NTP client will not sync if it is too far off from the current time it has. So try setting the date/time manually from your PC then sync it and see what happens.

 

[tmbrown97]

Also I had dns issues with mine so I now always find an actual IP Address to use.

Here's a decent chart:
http://tf.nist.gov/tf-cgi/servers.cgi

 

[cipherwar]

Yes, NTP won't correct something that is that far off. You have to manually set the clock to get it within at least a few minutes and then NTP should keep it in sync from there. This has nothing to do with ELK. NTP works that way on any platform or computer system.

 

[signal15]

Yes, NTP won't correct something that is that far off. You have to manually set the clock to get it within at least a few minutes and then NTP should keep it in sync from there. This has nothing to do with ELK. NTP works that way on any platform or computer system.

Sort of. Most systems need to be within 5 mins. But it does vary. I've used some devices that don't care and will update even if they are off by years. In any case, NTP no workie for me, even though I set the clock from a workstation that is synced with NTP. I'm using a dns name though, I'll have to update it to an IP and see. The clock skews very quickly if you aren't updating with NTP.