[ntp:questions] ntpd (4.2.2p1) stays "synchronized to LOCAL"

Danny Mayer mayer at ntp.isc.org
Tue Dec 5 03:07:25 UTC 2006


Jordan Russell wrote:
> My ntpd is no longer synchronizing with the servers specified in
> ntp.conf, and I'm having trouble figuring out why.
> 
> ntp.conf looks like this:
> 
> restrict default kod nomodify notrap nopeer noquery
> restrict -6 default kod nomodify notrap nopeer noquery

I believe that this is a duplicate line to the one above since default
is not specific to any IP stack.

> restrict 127.0.0.1
> restrict -6 ::1

You are not running an IPv6 stack so there's no purpose to this.

> restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
> server ntppub.tamu.edu
> server ntp1.cs.wisc.edu
> server ntp-2.cso.uiuc.edu

You want to add iburst to each of these server lines to synch quickly.

> server  127.127.1.0     # local clock
> fudge   127.127.1.0 stratum 10
> driftfile /var/lib/ntp/drift
> keys /etc/ntp/keys
> 
> After 58 minutes of uptime, "ntpq -p" shows:
> 
>      remote           refid      st t when poll reach   delay   offset
> jitter
> ==============================================================================
>  ntp3.tamu.edu   128.194.254.7    2 u  386 1024  377   25.258  25459.4
> 8473.45
>  caesar.cs.wisc. 128.105.201.11   2 u  383 1024  377   51.257  25474.1
> 8473.20
>  ntp-2.gw.uiuc.e 128.174.38.133   2 u  442 1024  377   56.901  16496.2
> 8492.19
> *LOCAL(0)        .LOCL.          10 l   49   64  377    0.000    0.000
>  0.001
> 
> /var/log/messages shows:
> 
> Dec  4 15:38:02 ntpdate[16513]: step time server 128.194.254.9 offset
> 14.354204 sec

Why are you doing this instead of just using the ntpd -g option?

> Dec  4 15:38:02 ntpd[16517]: ntpd 4.2.2p1 at 1.1570-o Fri Aug 18 13:04:14
> UTC 2006 (1)
> Dec  4 15:38:02 ntpd[16518]: precision = 1.000 usec
> Dec  4 15:38:02 ntpd[16518]: Listening on interface wildcard,
> 0.0.0.0#123 Disabled
> Dec  4 15:38:02 ntpd[16518]: Listening on interface lo, 127.0.0.1#123
> Enabled
> Dec  4 15:38:02 ntpd[16518]: Listening on interface eth0,
> 192.168.1.1#123 Enabled
> Dec  4 15:38:02 ntpd[16518]: Listening on interface eth1,
> 76.187.xx.xx#123 Enabled
> Dec  4 15:38:02 ntpd[16518]: kernel time sync status 0040
> Dec  4 15:38:02 ntpd[16518]: getaddrinfo: "::1" invalid host address,
> ignored

You are not running IPv6, hence the error.

> Dec  4 15:38:02 ntpd[16518]: frequency initialized 72.808 PPM from
> /var/lib/ntp/drift
> Dec  4 15:41:17 ntpd[16518]: synchronized to LOCAL(0), stratum 10
> Dec  4 15:41:17 ntpd[16518]: kernel time sync enabled 0001
> 
> When ntpd is in this state, the clock loses roughly half a second every
> minute, or about 10 minutes after a day of uptime (!).
> 
> I'm not sure if it's relevant, but I first noticed this problem about a
> month ago around the time ntp was upgraded from 4.2.0a to 4.2.2p1 (as
> part of upgrading from Fedora Core 5 and Fedora Core 6). Prior to that,
> the system ran ntpd for years without any issues.
> 

Multiple changes at the same time make things much more difficult to pin
down.

> Any idea why this is happening?
> 
> P.S. This is a Pentium III machine running an Intel D815EEA motherboard
> (i815 chipset). Linux 2.6.18.5 kernel.
> 

Have you looked at
http://ntp.isc.org/bin/view/Support/KnownOsIssues#Section_9.2.4. which
discusses issues with Linux and the 2.6 Kernel?

Danny




More information about the questions mailing list