Re: [gentoo-user] Latest unstable ntp not generating ntp.drift file.

[Dale]

William Kenworthy wrote:
>
> Dale, can you post (a sanitised) version of what 'ntpq -p' gives after
> ntpd has been running for some time, and the sanitised result of
> 'ntptrace.  Also include your full (sanitised) ntp.conf
> and /etc/conf.d/ntpd.
>
> This might help us see more detail of what is happening.
>
> BillK
>
> * sanitised - obfuscate public IP's only.
>
>


I should have posted this a while back.  Here we go:

root@fireball / # ntpq -p
      remote           refid      st t when poll reach   delay   offset  
jitter
==============================================================================
+triangle.kansas 128.252.19.1     2 u    4   64  127   56.270  673.749 
238.194
+B1-66ER.matrix. 192.43.244.18    2 u   14   64  377   75.505  672.846 
165.087
+kallisti.us     208.90.144.52    3 u   22   64  377   62.917  663.831 
168.738
*kazilik.haqr.ne 209.51.161.238   2 u   42   64  377   66.483  653.962 
166.119
root@fireball / # ntptrace
localhost: stratum 16, offset 0.000000, synch distance 0.000240
root@fireball / #

This is ntp.conf but I omitted the parts that are commented out.


server  64.6.144.6
server  67.159.5.90
server  67.59.168.233
server  204.62.14.98

driftfile    /var/lib/ntp/ntp.drift

restrict default nomodify nopeer
restrict 127.0.0.1

This makes sense if you read the command:

root@fireball / # cat /var/log/messages | grep ntp | tail -n 30
Jan  6 19:58:14 localhost ntpd[3017]: Attemping to register mDNS
Jan  6 19:58:14 localhost ntpd[3017]: *** WARNING *** The program 'ntpd' 
uses the Apple Bonjour compatibility layer of Avahi.
Jan  6 19:58:14 localhost ntpd[3017]: *** WARNING *** Please fix your 
application to use the native API of Avahi!
Jan  6 19:58:14 localhost ntpd[3017]: *** WARNING *** For more 
information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=ntpd>
Jan  6 19:58:14 localhost ntpd[3019]: precision = 1.000 usec
Jan  6 19:58:14 localhost ntpd[3019]: Listening on interface #0 
wildcard, 0.0.0.0#123 Disabled
Jan  6 19:58:14 localhost ntpd[3019]: Listening on interface #1 
wildcard, ::#123 Disabled
Jan  6 19:58:14 localhost ntpd[3019]: Listening on interface #2 eth0, 
fe80::1e6f:65ff:fe4c:91c7#123 Enabled
Jan  6 19:58:14 localhost ntpd[3019]: Listening on interface #3 lo, 
::1#123 Enabled
Jan  6 19:58:14 localhost ntpd[3019]: Listening on interface #4 lo, 
127.0.0.1#123 Enabled
Jan  6 19:58:14 localhost ntpd[3019]: Listening on interface #5 eth0, 
192.168.2.5#123 Enabled
Jan  6 19:58:14 localhost ntpd[3019]: kernel time sync status 2040
Jan  6 19:58:14 localhost ntpd[3019]: frequency initialized 500.000 PPM 
from /var/lib/ntp/ntp.drift
Jan  6 20:02:33 localhost ntpd[3019]: synchronized to 67.59.168.233, 
stratum 3
Jan  6 20:02:33 localhost ntpd[3019]: time reset +0.237917 s
Jan  6 20:02:33 localhost ntpd[3019]: kernel time sync status change 2001
Jan  6 20:07:31 localhost ntpd[3019]: synchronized to 67.159.5.90, stratum 2
Jan  6 20:13:57 localhost ntpd[3019]: synchronized to 204.62.14.98, 
stratum 2
Jan  6 20:17:34 localhost ntpd[3019]: time reset +0.567387 s
Jan  6 20:24:05 localhost ntpd[3019]: synchronized to 67.159.5.90, stratum 2
Jan  6 20:27:05 localhost ntpd[3019]: synchronized to 204.62.14.98, 
stratum 2
Jan  6 20:31:40 localhost ntpd[3019]: synchronized to 67.159.5.90, stratum 2
Jan  6 20:35:33 localhost ntpd[3019]: time reset +0.604521 s
Jan  6 20:44:29 localhost ntpd[3019]: synchronized to 67.159.5.90, stratum 2
Jan  6 20:47:44 localhost ntpd[3019]: synchronized to 204.62.14.98, 
stratum 2
Jan  6 20:55:22 localhost ntpd[3019]: time reset +0.663361 s
Jan  6 21:01:22 localhost ntpd[3019]: synchronized to 204.62.14.98, 
stratum 2
Jan  6 21:04:05 localhost ntpd[3019]: synchronized to 67.159.5.90, stratum 2
Jan  6 21:08:40 localhost ntpd[3019]: synchronized to 204.62.14.98, 
stratum 2
Jan  6 21:17:01 localhost ntpd[3019]: time reset +0.676538 s
root@fireball / #

Notice it is off about .6 seconds every 15 to 20 minutes or so?  It 
never gets any closer than this either.  I let it run for a good day the 
other day and it was still the same.  On my old rig, it would get to a 
point where the corrections were smaller and the syncs were father 
apart.  I have seen it go for hours between syncs and be only .01 or .02 
seconds off.  My old rig wouldn't sync so often either.  The drift file 
would also change and be some rather odd numbers.  The file on this rig 
never changes and looks like some sort of a default value.  Speaking of:

root@fireball / # cat /var/lib/ntp/ntp.drift
500.000
root@fireball / #

This is the adjtime file from a good ways back:

root@fireball / # cat /etc/adjtime
0.000000 1294340368 0.000000
1294340368
UTC
root@fireball / #

And the current one after some updates:

root@fireball / # cat /etc/adjtime
0.000000 1294365381 0.000000
1294365381
UTC
root@fireball / #

Does any of this put the light on something I may be missing?

I started with a copy of ntp.conf from my old rig.  I did change the 
servers but I change them sometimes anyway.  I use netselect or 
something to find the closest and fastest one to get a accurate clock.

Hoping for ideas.  Redoing adjtime doesn't seem to have helped.

Dale

:-)  :-)