[ntp:questions] Bizarre ntpdate behavior. Listing server as stratum 0 ?

elickd at one.net elickd at one.net
Fri May 20 19:01:15 UTC 2005


I realize that the following example is not a normal usage of ntpdate,
but the results it returns are very odd:


# ntpdate -qd ntp2 ntp2 ntp2

20 May 14:53:30 ntpdate[4069]: ntpdate 3-5.92d Mon Jul 27 19:20:17 PDT
1998 (1)
transmit(10.254.8.31)
receive(10.254.8.31)
transmit(10.254.8.31)
receive(10.254.8.31)
transmit(10.254.8.31)
receive(10.254.8.31)
transmit(10.254.8.31)
receive(10.254.8.31)
transmit(10.254.8.31)
transmit(10.254.8.31)
receive(10.254.8.31)
receive: pkt.org and peer.xmt differ
transmit(10.254.8.31)
receive(10.254.8.31)
receive: pkt.org and peer.xmt differ
transmit(10.254.8.31)
receive(10.254.8.31)
receive: pkt.org and peer.xmt differ
transmit(10.254.8.31)
receive(10.254.8.31)
receive: pkt.org and peer.xmt differ
transmit(10.254.8.31)
receive(10.254.8.31)
receive: pkt.org and peer.xmt differ
transmit(10.254.8.31)
receive(10.254.8.31)
receive: pkt.org and peer.xmt differ
transmit(10.254.8.31)
receive(10.254.8.31)
receive: pkt.org and peer.xmt differ
transmit(10.254.8.31)
receive(10.254.8.31)
receive: pkt.org and peer.xmt differ
transmit(10.254.8.31)
transmit(10.254.8.31)
server 10.254.8.31, port 123
stratum 4, precision -18, leap 00, trust 000
refid [10.254.81.9], delay 0.02557, dispersion 0.00198
transmitted 4, in filter 4
reference time:	   c638ae6c.40e95faa  Fri, May 20 2005 14:43:56.253
originate timestamp: c638b0aa.c89656ee  Fri, May 20 2005 14:53:30.783
transmit timestamp:  c638b0aa.c7ae1000  Fri, May 20 2005 14:53:30.779
filter delay:  0.02557  0.02560  0.02560  0.02560
		   0.00000  0.00000  0.00000  0.00000
filter offset: -0.00079 0.000598 0.002184 0.003539
		   0.000000 0.000000 0.000000 0.000000
delay 0.02557, dispersion 0.00198
offset -0.000794

server 10.254.8.31, port 123
stratum 0, precision 0, leap 00, trust 000
refid [0.0.0.0], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time:	   00000000.00000000  Thu, Feb  7 2036  1:28:16.000
originate timestamp: 00000000.00000000  Thu, Feb  7 2036  1:28:16.000
transmit timestamp:  c638b0ad.fae14000  Fri, May 20 2005 14:53:33.979
filter delay:  0.00000  0.00000  0.00000  0.00000
		   0.00000  0.00000  0.00000  0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
		   0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

server 10.254.8.31, port 123
stratum 0, precision 0, leap 00, trust 000
refid [0.0.0.0], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time:	   00000000.00000000  Thu, Feb  7 2036  1:28:16.000
originate timestamp: 00000000.00000000  Thu, Feb  7 2036  1:28:16.000
transmit timestamp:  c638b0ae.2e148000  Fri, May 20 2005 14:53:34.180
filter delay:  0.00000  0.00000  0.00000  0.00000
		   0.00000  0.00000  0.00000  0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
		   0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

20 May 14:53:35 ntpdate[4069]: adjust time server 10.254.8.31 offset
-0.000794 sec


So are the stratum 0, offset 0 returns due to a bug in ntpdate, the
flood of queries being sent to the same box or erratic behavior on the
NTP server I'm querying?




More information about the questions mailing list