On 2008-05-23, Harlan Stenn <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] writes: > >> the time on one of our servers is incorrect despite using ntpd, I >> also noticed that the driftfile value is 0.000 and doesn't changed. >> What could be the problem? >> >> Here is our conf file: >> >> restrict default kod nomodify notrap nopeer noquery >> restrict -6 default kod nomodify notrap nopeer noquery >> restrict 127.0.0.1 >> restrict -6 ::1 > > Please read http://support.ntp.org/Support/AccessRestrictions .
There is nothing in the OP's restrictions which block time service. However something else may be blocking the polls of the remote time servers. >> server 0.nl.pool.ntp.org >> server 1.nl.pool.ntp.org >> server 2.nl.pool.ntp.org >> server 3.nl.pool.ntp.org Those hostnames are valid and resolves to multiple IP addresses. With these server lines it will take ntpd ~ 5 minutes to achieve initial synchronization (assuming it is able to poll the remote time servers). If that is not fast enough for the OP's application then 'iburst' should be appended to the server lines and the initial sync time will be reduced to less than 20 seconds. Contrary to some misleading comments made in this news-group, iburst does not unnecessarily load the remote time servers and is generally considered acceptable to use. >> fudge 127.127.1.0 stratum 10 That line does nothing because the Undisciplined Local Clock has not been configured. >> keys /etc/ntp/keys That line does nothing because the symmetric key configuration is imcomplete. >> logconfig =all Does ntp 4.2.2p1 support this configuration directive? > You can use 'ntpq -p' to see if you are syncing to any machines. We need to see the output of ntpq -p to be able to diagnose the OP's problem. -- Steve Kostecke <[EMAIL PROTECTED]> NTP Public Services Project - http://support.ntp.org/ _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
