Hello,
One of my systems had been running for ~6 weeks. During this time,
the frequency offset computed by ntpd remained stable between
-6.6 ppm and -6.2 ppm.
On April 30, the time offset started climbing and reached 14 ms in
approximately 90 minutes. ntpd started bumping the frequency offset,
down to -9.4 ppm.
Today, the frequency offset remains around -9.4 ppm.
(And the time offset stays below 1 ms).
# ntpq -crv
assID=0 status=06f4 leap_none, sync_ntp, 15 events, event_peer/strat_chg,
version="ntpd [EMAIL PROTECTED] Fri Mar 16 10:45:43 UTC 2007 (1)",
processor="i686", system="Linux/2.6.22.1-rt9", leap=00, stratum=2,
precision=-20, rootdelay=45.975, rootdispersion=29.674, peer=33229,
refid=134.226.81.3,
reftime=cbc5889f.3df5b689 Fri, May 2 2008 12:33:35.242, poll=8,
clock=cbc58c94.38f8bda6 Fri, May 2 2008 12:50:28.222, state=4,
offset=0.099, frequency=-9.373, jitter=0.849, noise=0.699,
stability=0.002
One of the servers I use seems to have gone crazy:
remote st t when poll reach delay offset jitter
==============================================================
212.27.63.123 5 u 235 256 377 27.929 759.246 1.475
But I use several other servers, which all agree.
Can someone offer an explanation for the sudden jump in the system
clock's frequency offset?
Regards.
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.org/mailman/listinfo/questions
