[ntp:questions] Severe time drift for Undisciplined Local Clock

[Steve Kostecke]

On 2007-04-10, deon at nulan.co.za <deon at nulan.co.za> wrote:

> I am calling ntpd like this:
>
> ntpd -A -l /var/log/ntp/main.log

-A means "Do not require cryptographic authentication for broadcast
client, multicast client and symmetric passive associations." If you're
not using one of those modes this option does nothing for you.

You can specify the ntp log file inside ntp.conf instead of on the
command line.

> My /etc/ntp.conf file has one line:
>
> server 192.168.222.100

Your ntp.conf does not specify a drift file. This causes ntpd to perform
a 15 minute clock evaluation every time it starts up.

Your ntp.conf should look like this:

logfile /var/log/ntp/main.log
driftfile /var/lib/ntp/ntp.drift

>remote            refid  st t when poll reach delay  offset jitter
> 192.168.222.100 .LOCL.   1 u   55   64  377  0.327 -418554 147.741

192.168.222.100 has an unreasonable offset and should not be claiming to
be stratum 1 (because it is using the undisciplined local clock).

> ntpq> rv 61380
> assID=61380 status=9014 reach, conf, 1 event, event_reach,
> srcadr=192.168.222.100, srcport=123, dstadr=192.168.222.200,
> dstport=123, leap=00, stratum=1, precision=-6, rootdelay=0.000,
> rootdispersion=10414.490, refid=LOCL, reach=377, unreach=0, hmode=3,

The rootdispersion is too high.

> pmode=4, hpoll=6, ppoll=10, flash=00 ok, keyid=0, ttl=0,
> offset=-418554.281, delay=0.327, dispersion=18.791, jitter=168.096,

The offset is too high.

> reftime=c9c5b3b5.e4000000  Tue, Apr 10 2007  8:56:53.890,
> org=c9c63a54.e8000000  Tue, Apr 10 2007 18:31:16.906,
> rec=c9c63bf7.bf0f27bb  Tue, Apr 10 2007 18:38:15.746,
> xmt=c9c63bf7.bed8904f  Tue, Apr 10 2007 18:38:15.745,

You need to fix 192.168.222.100 first.

-- 
Steve Kostecke <kostecke at ntp.isc.org>
NTP Public Services Project - http://ntp.isc.org/