On 16 January 2012 12:31, Tim Connors <tconnors@rather.puzzling.org> wrote:
On Sun, 15 Jan 2012, Andrew Worsley wrote:
Any suggestions on logging more info to find the cause or deeper insights into what is going wrong would be appreciated.
More logs with these settings:
logfile /var/log/ntpd statsdir /var/log/ntpstats/ statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable
(don't forget to logrotate!)
Probably won't show anything other than time went off by a small amount.
.... Hmm got some complaints about syntax errors - turns out to be old configuration settings ... see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637941 and this http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616684 and also default flag on restrict appears appears to cause complaints. See if it makes any difference...
warrane.connect.com.au (192.189.54.33) got dodgy hardware? (do a check_ntp from your host against another ntp server perhaps, then compare against warrane.connect.com.au). ntptrace show anything?
All ntp servers looked okay when I checked currently: config(3)# check_ntp -H warrane.connect.com.au NTP OK: Offset 0.4516801834 secs|offset=0.451680s;60.000000;120.000000; config(0)# check_ntp -H yarrina.connect.com.au NTP OK: Offset 0.5105582476 secs|offset=0.510558s;60.000000;120.000000; config(0)# check_ntp -H ns0.eftel.com NTP OK: Offset 0.5307137966 secs|offset=0.530714s;60.000000;120.000000; config(0)# ntptrace localhost: stratum 3, offset 0.122603, synch distance 0.038587 yarrina.connect.com.au: stratum 2, offset -0.000213, synch distance 0.033050 130.95.179.80: timed out, nothing received ***Request timed out
Writing a DVD just before? DMA accidentally turned itself off?
-- Tim Connors
See if the statistics show up anything - need to dig out the documentation to understand it. Thanks Andrew