Author Topic: Time drift  (Read 2631 times)

Offline ddog511

  • Contributer
  • *
  • Posts: 24
  • Country: us
  • Karma: +0/-0
    • View Profile
Time drift
« on: February 10, 2023, 09:52:45 AM »
Having an issue with one of my MXe-III controllers running 9.2 where the clock is lagging.  Over the past 2 weeks, I've reset the clock a few times.  This week I started to document the time differences.  I set it on Wednesday morning and it was about 2 seconds ahead of network time at that point.  24 hours later and it was already 20 seconds behind.  This morning, it was 50 seconds behind.  It was initially set to use our NTP server for time, but then it was showing 7 minutes behind despite the NTP server being spot on.  I've also tried syncing with nist.gov and even Google's public NTP server but had similar issues.  Any ideas what might be causing this?  I have a few other controllers doing similar but this specific controller is the most extreme.


Offline ZuluAlpha

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 693
  • Country: us
  • Karma: +17/-0
    • View Profile
Re: Time drift
« Reply #1 on: February 10, 2023, 01:23:19 PM »
I don't have a 9.2 but that's really strange with NTP set. Usually I see in the logs where they sync with the NTP server overnight. Are these hardware or virtual?

Offline johnp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2202
  • Country: us
  • Karma: +66/-0
    • View Profile
Re: Time drift
« Reply #2 on: February 10, 2023, 01:34:15 PM »
NTP available?

Offline ddog511

  • Contributer
  • *
  • Posts: 24
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: Time drift
« Reply #3 on: February 10, 2023, 02:14:48 PM »
These are physical boxes and we had them on NTP initially.  When I was informed about the time issue, I took it off NTP and set the time and then put it back on NTP.  Within a week is was several minutes behind again.  So this past weekend, I rebooted them all and on this one in particular, manually set the time and left it that way. 

Offline ZuluAlpha

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 693
  • Country: us
  • Karma: +17/-0
    • View Profile
Re: Time drift
« Reply #4 on: February 10, 2023, 03:31:20 PM »
When it's on NTP does it show that it syncs in the log?

Offline ddog511

  • Contributer
  • *
  • Posts: 24
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: Time drift
« Reply #5 on: February 10, 2023, 04:30:22 PM »
Assuming I'm looking at the right log (e-smith/sync) I see a lot of entries much like the following:

800.0=sync|status|success|SyncTime|1674839945
801.0=sync|status|success|SyncTime|1674926346
802.0=sync|status|success|SyncTime|1675012745
803.0=sync|status|success|SyncTime|1675099145
804.0=sync|status|success|SyncTime|1675185547
805.0=sync|status|success|SyncTime|1675271945
806.0=sync|status|success|SyncTime|1675358345
807.0=sync|status|success|SyncTime|1675444745
808.0=sync|status|success|SyncTime|1675531145
809.0=sync|status|success|SyncTime|1675566268
810.0=sync|status|success|SyncTime|1675617545
811.0=sync|status|success|SyncTime|1675703944
812.0=sync|status|success|SyncTime|1675790344
813.0=sync|status|success|SyncTime|1675876745
814.0=sync|status|success|SyncTime|1675963145
815.0=sync|status|success|SyncTime|1676049544

If this is not the correct log, let me know which one I should be looking at

Offline lundah

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1216
  • Country: us
  • Karma: +66/-0
  • Senior Chief Grunt
    • View Profile
Re: Time drift
« Reply #6 on: February 10, 2023, 05:25:45 PM »
Assuming I'm looking at the right log (e-smith/sync) I see a lot of entries much like the following:

800.0=sync|status|success|SyncTime|1674839945
801.0=sync|status|success|SyncTime|1674926346
802.0=sync|status|success|SyncTime|1675012745
803.0=sync|status|success|SyncTime|1675099145
804.0=sync|status|success|SyncTime|1675185547
805.0=sync|status|success|SyncTime|1675271945
806.0=sync|status|success|SyncTime|1675358345
807.0=sync|status|success|SyncTime|1675444745
808.0=sync|status|success|SyncTime|1675531145
809.0=sync|status|success|SyncTime|1675566268
810.0=sync|status|success|SyncTime|1675617545
811.0=sync|status|success|SyncTime|1675703944
812.0=sync|status|success|SyncTime|1675790344
813.0=sync|status|success|SyncTime|1675876745
814.0=sync|status|success|SyncTime|1675963145
815.0=sync|status|success|SyncTime|1676049544

If this is not the correct log, let me know which one I should be looking at

That's the license synch log. Look in ntpd/current.

Offline ddog511

  • Contributer
  • *
  • Posts: 24
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: Time drift
« Reply #7 on: February 13, 2023, 08:36:02 AM »
I don't see an ntpd/current log.  Is there a way to view it via a maintenance command?  It's not listed in the Server Manager logs.

Offline ZuluAlpha

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 693
  • Country: us
  • Karma: +17/-0
    • View Profile
Re: Time drift
« Reply #8 on: February 13, 2023, 09:33:10 AM »
I don't see an ntpd/current log.  Is there a way to view it via a maintenance command?  It's not listed in the Server Manager logs.

Should be a daily SystemDateTime entry in the "All Software Logs" section (will also be in "All Maintenance/Software Logs"). Mine seem to be at 5am local time but not sure if that's a standard thing or just when mine go. Adjusting 3-4 seconds per day.

Offline ddog511

  • Contributer
  • *
  • Posts: 24
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: Time drift
« Reply #9 on: February 13, 2023, 10:50:00 AM »
I definitely don't have any entries like that.  I wonder if I'm more locked down than they say I am.

Offline johnp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2202
  • Country: us
  • Karma: +66/-0
    • View Profile
Re: Time drift
« Reply #10 on: February 16, 2023, 05:55:32 PM »
FWIW, NTP will keep this inline and if you see logs regarding failure, the clock can drift beyond a point of recovery. You then need to get the system close to actual before resuming NTP


 

Sitemap 1 2 3 4 5 6 7 8 9 10