On Thu, Feb 14, 2008 at 09:35:11AM -0600, Moshe Yudkowsky wrote: > > > 10 Feb 10:17:37 ntpd[15698]: system event 'event_peer/strat_chg' (0x04) > status 'sync_alarm, sync_ntp, 2 events, event_restart' (0xc621) > 10 Feb 10:17:37 ntpd[15698]: synchronized to 216.184.20.83, stratum 3 > 10 Feb 10:17:38 ntpd[15698]: time reset +1.456355 s > 10 Feb 10:17:38 ntpd[15698]: kernel time sync status change 0001 [...] > # ntpdc -c peers -c sysinfo > remote local st poll reach delay offset disp > ======================================================================= > =clock.trit.net 172.28.54.162 2 64 377 0.07658 24.532540 0.07133 > =63.240.161.99 172.28.54.162 2 64 377 0.01187 26.785723 0.06363 > =mick.eng.uiowa. 172.28.54.162 2 64 377 0.01299 32.043092 0.04242 > =hydrogen.cert.u 172.28.54.162 2 64 377 0.08910 36.593320 0.03636 > =bagpipes.local 172.28.54.162 2 64 377 0.00017 27.291048 0.06699 > =nick125.com 172.28.54.162 3 64 377 0.12784 34.653144 0.04703 > =nist1.symmetric 172.28.54.162 1 64 0 0.00000 0.000000 3.99217 > =dtype.org 172.28.54.162 2 64 377 0.06665 33.784147 0.05498
It's seeing peers that are off between 24 and 36 seconds. It can't seem to find 2 peers that agree on the time, and they're off in the order of seconds. >From what I get this is after about 20 minutes. That would mean you have a drift of about 30000 ppm. ntpd will not be able to deal with such big drifts. This is ussually a kernel problem. I suggest you try a different version of the kernel. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
