On 2008-05-28, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >> [EMAIL PROTECTED] writes: >> chantal> Hi list, the time on one of our servers is incorrect despite using >> chantal> ntpd, I also noticed that the driftfile value is 0.000 and doesn't >> chantal> changed. What could be the problem? >> chantal> Here is our conf file: >> >> Please read http://support.ntp.org/Support/AccessRestrictions . >> >> You can use 'ntpq -p' to see if you are syncing to any machines. > > Hi this, is the ntpq -p output: > > [EMAIL PROTECTED] ~]# ntpq -p > remote refid st t when poll reach delay offset jitter >============================================================================ > sectionzero.org 35.65.96.0 3 u 171 1024 376 2.065 347330. 4621.34 > steghoefer.eu 87.239.10.190 3 u 200 1024 377 2.182 351371. 4446.79 > nieuwland-240.c 213.136.12.53 3 u 132 1024 377 0.728 347218. 4448.43 > fw-enschede-6.i 193.190.230.65 2 u 201 1024 377 5.566 346919. 4457.15 >*LOCAL(0) .LOCL. 10 l 33 64 377 0.000 0.000 0.001
The problem here is that your ntpd is following the (fake) Undisciplined Local Clock instead of the (real) Remote Time Servers. The Undisciplined Local Clock is a kludge to allow an ntpd to claim to be synchronised even when it isn't. This capability is only useful if the ntpd is serving time to others. But, as you can see, undesireable things can happen. Please try commenting out the local clock and restarting ntpd. You may want to run 'ntpd -gq' before starting ntpd in daemon mode to preset the time. -- Steve Kostecke <[EMAIL PROTECTED]> NTP Public Services Project - http://support.ntp.org/ _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
