[ntp:questions] "No association ID's returned" after a period of time

David Lord snews at lordynet.org
Fri Aug 28 07:40:00 UTC 2009


Brian J. Murrell wrote:
> [ repost given my last one never showed up on the group.  apologies in
> advance for duplicates. ]
> 
> Hello.
> 
> I have an NTP server here in my network which I use to sync from some
> servers on the Internet and then I sync my local network's clocks to it.
> 
> For some time now, this local time reference server has been losing it's
> peers as such:
> 
> # echo peers | ntpq
> No association ID's returned
> 
> If I simply restart the server, it will again sync with it's peers and
> things will be good for a while again, but eventually, the above will
> re-occur.
> 
> My configuration is as follows:
> 
> driftfile /var/lib/ntp/ntp.drift
> statistics loopstats peerstats clockstats
> filegen loopstats file loopstats type day enable
> filegen peerstats file peerstats type day enable
> filegen clockstats file clockstats type day enable
> server ca.pool.ntp.org
> server ca.pool.ntp.org
> server pool.ntp.org
> server ntp.ubuntu.com
> restrict -4 default kod notrap nomodify nopeer noquery
> restrict -6 default kod notrap nomodify nopeer noquery
> restrict 127.0.0.1
> restrict ::1
> 
> Any ideas as to why this might be happening, or hints on how to debug
> it?
> 
> The version of the ntpd server on this troubled machine is:
> 
> ntpd 4.2.4p4 at 1.1520-o Wed May 13 21:05:57 UTC 2009 (1)
> 
> Startup messages from the restart I just initiated:
> 
> Aug 27 09:47:19 linux ntpd[13347]: ntpd 4.2.4p4 at 1.1520-o Wed May 13 21:05:57 UTC 2009 (1)
> Aug 27 09:47:19 linux ntpd[13348]: precision = 1.000 usec
> Aug 27 09:47:19 linux ntpd[13348]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
> Aug 27 09:47:19 linux ntpd[13348]: Listening on interface #1 wildcard, ::#123 Disabled
> Aug 27 09:47:19 linux ntpd[13348]: Listening on interface #2 lo, ::1#123 Enabled
> Aug 27 09:47:19 linux ntpd[13348]: Listening on interface #3 eth0, 1234:5678:919:0:7a3:a2ee:ef1a:8b74#123 Enabled
> Aug 27 09:47:19 linux ntpd[13348]: Listening on interface #4 eth0, fe80::2d0:a2ee:ef1a:8b74#123 Enabled
> Aug 27 09:47:19 linux ntpd[13348]: Listening on interface #5 lo, 127.0.0.1#123 Enabled
> Aug 27 09:47:19 linux ntpd[13348]: Listening on interface #6 eth0, 10.75.22.3#123 Enabled
> Aug 27 09:47:19 linux ntpd[13348]: Listening on interface #7 eth0:1, 10.75.22.8#123 Enabled
> Aug 27 09:47:19 linux ntpd[13348]: kernel time sync status 0040
> Aug 27 09:47:19 linux ntpd[13348]: frequency initialized -29.254 PPM from /var/lib/ntp/ntp.drift
> 
> Listing peers now shows:
> 
> # echo peers | ntpq
>      remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
>  ip-174-142-75-1 129.128.5.210    2 u   11   64    7   23.005  45866.3   1.393
>  zeus.yocum.org  65.212.71.102    2 u   11   64    7   21.446  45862.0   2.440
>  p1-ha-inbound-g 136.159.2.9      3 u    7   64    7   76.035  45861.4   0.943
>  europium.canoni 193.79.237.14    2 u    9   64    7  114.840  45860.0   1.409
> 
> Thanx in advance for any hints you can provide!
> 

Only time I see this is when I've lost internet connection for
a long enough period (many hours rather than minutes). Also
if the hosts can't be contacted when ntpd is started then none
of servers are added.

Ntpd actually seems quite good as a monitor for quality of my
internet connection or picking up problems in routes to the
various servers.

David




More information about the questions mailing list