excessive time drift

Z

zachw

Hi all!

Just installed 15.0-RELEASE on an Intel NUC and am observing some serious time drift.

Code: 
$ sudo ntpd -q
Password:
 9 Dec 09:58:35 ntpd[3186]: ntpd 4.2.8p18-a (1): Starting
 9 Dec 09:58:35 ntpd[3186]: Command line: ntpd -q
 9 Dec 09:58:35 ntpd[3186]: ----------------------------------------------------
 9 Dec 09:58:35 ntpd[3186]: ntp-4 is maintained by Network Time Foundation,
 9 Dec 09:58:35 ntpd[3186]: Inc. (NTF), a non-profit 501(c)(3) public-benefit
 9 Dec 09:58:35 ntpd[3186]: corporation.  Support and training for ntp-4 are
 9 Dec 09:58:35 ntpd[3186]: available at https://www.nwtime.org/support
 9 Dec 09:58:35 ntpd[3186]: ----------------------------------------------------
 9 Dec 09:58:35 ntpd[3186]: proto: precision = 0.092 usec (-23)
 9 Dec 09:58:35 ntpd[3186]: basedate set to 2018-08-07
 9 Dec 09:58:35 ntpd[3186]: gps base set to 2018-08-12 (week 2014)
 9 Dec 09:58:35 ntpd[3186]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): stat failed: No such file or directory
 9 Dec 09:58:37 ntpd[3186]: Soliciting pool server 23.186.168.132
 9 Dec 09:58:37 ntpd[3186]: Soliciting pool server 198.71.50.75
 9 Dec 09:58:38 ntpd[3186]: Soliciting pool server 162.244.81.139
 9 Dec 09:58:38 ntpd[3186]: Soliciting pool server 23.150.41.123
 9 Dec 09:58:38 ntpd[3186]: Soliciting pool server 144.202.41.38
 9 Dec 09:58:39 ntpd[3186]: Soliciting pool server 216.229.0.50
 9 Dec 09:58:39 ntpd[3186]: Soliciting pool server 104.152.220.10
 9 Dec 09:58:40 ntpd[3186]: Soliciting pool server 99.28.14.242
 9 Dec 09:58:54 ntpd[3186]: ntpd: time set +6.169471 s
ntpd: time set +6.169471s

$ sudo ntpd -q
Password:
 9 Dec 10:06:12 ntpd[3699]: ntpd 4.2.8p18-a (1): Starting
 9 Dec 10:06:12 ntpd[3699]: Command line: ntpd -q
 9 Dec 10:06:12 ntpd[3699]: ----------------------------------------------------
 9 Dec 10:06:12 ntpd[3699]: ntp-4 is maintained by Network Time Foundation,
 9 Dec 10:06:12 ntpd[3699]: Inc. (NTF), a non-profit 501(c)(3) public-benefit
 9 Dec 10:06:12 ntpd[3699]: corporation.  Support and training for ntp-4 are
 9 Dec 10:06:12 ntpd[3699]: available at https://www.nwtime.org/support
 9 Dec 10:06:12 ntpd[3699]: ----------------------------------------------------
 9 Dec 10:06:12 ntpd[3699]: proto: precision = 0.064 usec (-24)
 9 Dec 10:06:12 ntpd[3699]: basedate set to 2018-08-07
 9 Dec 10:06:12 ntpd[3699]: gps base set to 2018-08-12 (week 2014)
 9 Dec 10:06:12 ntpd[3699]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): stat failed: No such file or directory
 9 Dec 10:06:13 ntpd[3699]: Soliciting pool server 50.251.160.20
 9 Dec 10:06:14 ntpd[3699]: Soliciting pool server 23.186.168.133
 9 Dec 10:06:14 ntpd[3699]: Soliciting pool server 66.205.249.28
 9 Dec 10:06:15 ntpd[3699]: Soliciting pool server 173.255.230.96
 9 Dec 10:06:15 ntpd[3699]: Soliciting pool server 23.155.72.147
 9 Dec 10:06:16 ntpd[3699]: Soliciting pool server 45.33.53.84
 9 Dec 10:06:16 ntpd[3699]: Soliciting pool server 168.235.69.132
 9 Dec 10:06:17 ntpd[3699]: Soliciting pool server 50.117.3.52
 9 Dec 10:06:45 ntpd[3699]: ntpd: time set +22.984768 s
ntpd: time set +22.984768s

So, clearly it's losing seconds over minutes.

This system was just recently running Windows with no similar symptoms.

Any insights as to what could be causing the problem or where to look for more details?

Thanks!
Zach
 
No clock is perfect, there's always some drift. It could be your ntpd.drift is a bit out of whack though and it tries to overcompensate. I'd remove /var/db/ntpd.drift, restart ntpd(8) and let it run for an hour or so. It should try to recalculate the drift. Then see if it's still way off the mark.

Code: 
   Frequency Discipline
     The ntpd behavior at startup depends on whether the frequency file,
     usually ntp.drift, exists.  This file contains the latest estimate of
     clock frequency error.  When the ntpd is started and the file does not
     exist, the ntpd enters a special mode designed to quickly adapt to the
     particular system clock oscillator time and frequency error.  This takes
     approximately 15 minutes, after which the time and frequency are set to
     nominal values and the ntpd enters normal mode, where the time and
     frequency are continuously tracked relative to the server.  After one
     hour the frequency file is created and the current frequency offset
     written to it.  When the ntpd is started and the file does exist, the
     ntpd frequency is initialized from the file and enters normal mode
     immediately.  After that the current frequency offset is written to the
     file at hourly intervals.
 
You must log in or register to reply here.
Back
Top