[ntp:questions] NTP gone awry
Steven Meres
steve at plymouthengineering.com
Tue Nov 22 19:06:38 UTC 2005
I noticed yesterday that the time was way off from what it should be (by
hours). Actually, I didn't notice it until I kept getting calls asking why
the time was so messed up. Anyway, I had to restart the server yesterday
and that's when it must have gone awry. Up until then everything was ok.
Well, since things weren't working very well I decided to change to a few
closer time servers. Now, it seems the offsets just get larger, not
smaller. Any ideas as to what I should do? I have posted my ntp.conf, a
few ntptraces, and a few ntpq - p queries.
fserver:~# ntpq -p
remote refid st t when poll reach delay offset
jitter
============================================================================
==
toshi.keneli.or .GPS. 1 u 4 64 3 46.560 56745.2
762.075
bonehed.lcs.mit .CDMA. 1 u 65 64 1 187.359 56678.7
0.001
NAVOBS1.MIT.EDU .PSC. 1 u 2 64 3 30.620 57545.7
777.275
192.168.0.255 .BCST. 16 u - 64 0 0.000 0.000
4000.00
fserver:~# ntpq -p
remote refid st t when poll reach delay offset
jitter
============================================================================
==
toshi.keneli.or .GPS. 1 u 11 64 3 46.560 56745.2
762.075
bonehed.lcs.mit .CDMA. 1 u 7 64 3 43.290 57569.2
890.558
NAVOBS1.MIT.EDU .PSC. 1 u 9 64 3 30.620 57545.7
777.275
192.168.0.255 .BCST. 16 u - 64 0 0.000 0.000
4000.00
fserver:~# ntpq -p
remote refid st t when poll reach delay offset
jitter
============================================================================
==
toshi.keneli.or .GPS. 1 u 26 64 377 48.615 62271.0
2927.46
bonehed.lcs.mit .CDMA. 1 u 18 64 377 26.627 62404.0
2904.85
NAVOBS1.MIT.EDU .PSC. 1 u 29 64 377 27.011 62268.5
2950.05
192.168.0.255 .BCST. 16 u - 64 0 0.000 0.000
4000.00
fserver:~# ntpq -p
remote refid st t when poll reach delay offset
jitter
============================================================================
==
toshi.keneli.or .GPS. 1 u 18 64 377 48.615 62271.0
2376.17
bonehed.lcs.mit .CDMA. 1 u 8 64 377 26.627 62404.0
2335.87
NAVOBS1.MIT.EDU .PSC. 1 u 19 64 377 27.011 62268.5
2325.22
192.168.0.255 .BCST. 16 u - 64 0 0.000 0.000
4000.00
fserver:~# ntpq -p
remote refid st t when poll reach delay offset
jitter
============================================================================
==
toshi.keneli.or .GPS. 1 u 10 64 377 42.842 72646.5
3516.33
bonehed.lcs.mit .CDMA. 1 u 4 64 377 26.363 75086.9
1993.59
NAVOBS1.MIT.EDU .PSC. 1 u 10 64 377 26.573 75013.1
1987.28
192.168.0.255 .BCST. 16 u - 64 0 0.000 0.000
4000.00
fserver:~# ntpq -p
remote refid st t when poll reach delay offset
jitter
============================================================================
==
toshi.keneli.or .GPS. 1 u 55 64 377 43.549 87708.2
2333.91
bonehed.lcs.mit .CDMA. 1 u 40 64 377 26.588 83887.1
3558.28
NAVOBS1.MIT.EDU .PSC. 1 u 44 64 377 26.843 85428.0
2336.30
192.168.0.255 .BCST. 16 u - 64 0 0.000 0.000
4000.00
fserver:~#
fserver:~# ntptrace time.keneli.org
time.keneli.org: stratum 1, offset 0.000003, synch distance 0.000361, refid
'GPS'
fserver:~# ntptrace bonehed.lcs.mit.edu
bonehed.lcs.mit.edu: stratum 1, offset 0.000017, synch distance 0.000838,
refid 'CDMA'
fserver:~# ntptrace navobs1.mit.edu
navobs1.mit.edu: stratum 1, offset -0.000001, synch distance 0.000391, refid
'PSC'
fserver:~#
fserver:~# cat /etc/ntp.conf
# /etc/ntp.conf, configuration for ntpd
# ntpd will use syslog() if logfile is not defined
logfile /var/log/ntpd
driftfile /var/lib/ntp/ntp.drift
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
# You do need to talk to an NTP server or two (or three).
server time.keneli.org
server bonehed.lcs.mit.edu
server navobs1.mit.edu
#server 127.127.1.0
#fudge 127.127.1.0 stratum 10
# By default, exchange time with everybody, but don't allow configuration.
# See /usr/share/doc/ntp-doc/html/accopt.html for details.
restrict default kod notrap nomodify nopeer noquery
# Local users may interrogate the ntp server more closely.
restrict 127.0.0.1 nomodify
broadcast 192.168.0.255
More information about the questions
mailing list