[19439] in Athena Bugs
linux 9.0.13: ntpd
daemon@ATHENA.MIT.EDU (Thomas E Cavin)
Fri Jul 27 14:16:58 2001
Message-Id: <200107271816.OAA01729@lap1-wccf.mit.edu>
To: bugs@MIT.EDU
Date: Fri, 27 Jul 2001 14:16:55 -0400
From: Thomas E Cavin <cavin@MIT.EDU>
System name: lap1-wccf.mit.edu
Type and version: i686 9.0.13
Display type: XFree86 3.3.6a Mach64
Shell: /bin/athena/bash
Window manager: sawfish
What were you trying to do?
Check to see if time was properly syncronized using
/usr/athena/bin/ntptrace
What's wrong:
The system has been up for over thirty minutes, is not yet
syncronized, and doesn't appear to have found a time server.
bash-2.04# /usr/athena/bin/ntptrace
localhost: stratum 16, offset 0.000024, synch distance 0.00327
0.0.0.0: *Not Synchronized*
bash-2.04# uptime
2:05pm up 33 min, 3 users, load average: 0.01, 0.02, 0.00
What should have happened:
The system should have used NTP to find a time server (and should
have found the router) and started to get into time synchronization.
The response to the simple ntptrace should have looked something
like this (below) except using localhost instead of Avanti.
bash-2.04# /usr/athena/bin/ntptrace avanti
AVANTI.MIT.EDU: stratum 4, offset 0.703359, synch distance 0.09044
E19-RTR-E25-ETHER.MIT.EDU: stratum 3, offset 0.708449, synch distance 0.07599
WHOS-THERE.MIT.EDU: stratum 2, offset 0.692900, synch distance 0.01608
NAVOBS1.MIT.EDU: stratum 1, offset 0.692350, synch distance 0.00189, refid 'USNO'
Please describe any relevant documentation references:
This is probably coming from the athena-ntp package. Behaviour
descriptions are from the NTP source distribution documentation (I'd
have to track down the references.)
