[ntp:questions] Re: ntpdc 'sysinfo' output inconsistent with ntpq-p output

Jan Ceuleers janspam.ceuleers at skynet.be
Tue Jul 25 14:57:27 UTC 2006


Danny Mayer wrote:
> Jan,
> 
> Which line is the incorrect refid?
> 
> Danny


Danny,

Referring back to the example in my earlier message, the following was 
the only line output by 'ntptrace localhost' (because it thought that 
localhost was at stratum 1 and therefore synchronised to its refclock):

localhost: stratum 1, offset 0.000087, synch distance 0.461839, refid '
'

The refid is supposed to be displayed in single quotes, which here seems 
to be an LF (newline). It displays like that even in an 80-column 
window; this is not a result of newsgroup word-wrapping.

This shows that the ntpq -n -c rv output had not yet caught on to the 
fact that the refclock had not yielded a valid sample for 976 seconds 
and that another server has been selected as the syspeer:

      remote           refid      st t when poll reach   delay   offset 
  jitter
==============================================================================
  LOCAL(0)        .LOCL.          10 l   52   64  377    0.000    0.000 
   0.001
  GENERIC(0)      .DCFa.           0 l  976   64    0    0.000   -2.266 
   0.001
+cerber.obs.coe. 145.238.110.68   3 u  386 1024  377   67.058    0.866 
0.244
*chronos.zedat.f .GPS.            1 u  363 1024  377   31.280    0.905 
0.440
-salukes.opensou 185.55.101.136   2 u  324 1024  377   14.834    2.596 
1.284
-217.71.122.144  80.190.252.238   3 u  327 1024  377   15.051   -4.640 
3.759
+ntp1.belbone.be 195.13.23.250    2 u  337 1024  377   10.421    1.627 
0.385
-time.ijs.si     193.2.4.2        2 u  331 1024  377   50.810    0.121 
0.045
-bear.zoo.bt.co. 194.81.227.227   2 u  327 1024  375   23.634    5.755 
1.546
  skr03.xperim.be 192.168.1.1      2 u  379 1024  377    0.760   -3.400 
   5.686


As I said, this is reproduceable. I've just run the same couple of 
commands again (ntptrace localhost; ntpq -p localhost) and this is the 
output:

localhost: stratum 1, offset 0.000497, synch distance 0.449679, refid 'ÕÞ
                                                                          Þ'
      remote           refid      st t when poll reach   delay   offset 
  jitter
==============================================================================
  LOCAL(0)        .LOCL.          10 l   24   64  377    0.000    0.000 
   0.001
  GENERIC(0)      .DCFa.           0 l  113   64  164    0.000  1262304 
1262304
-roxane.home-dn. 130.149.17.8     2 u  779 1024  377   13.128    4.907 
  1.264
-195.244.96.13   235.190.183.255  2 u  924 1024  377   17.820   40.431 
20.218
*n3.surbl.org    193.0.4.7        2 u  787 1024  377   10.977    1.743 
  2.962
-host-213-189-18 98.221.144.0     2 u  778 1024  377   13.678   17.895 
10.933
+tilia.zsx.hu    192.53.103.108   2 u  774 1024  377   36.650    0.513 
  0.541
-ntp1.belbone.be 195.13.23.250    2 u  770 1024  377    9.894    2.941 
  2.934
-time.ijs.si     193.2.4.2        2 u  780 1024  377   50.661    4.039 
  1.605
+bear.zoo.bt.co. 130.149.17.8     2 u  789 1024  377   24.860    0.708 
  2.960
-skr03.xperim.be 192.168.15.6     5 u  779 1024  377    0.741  -19.073 
58.959

Note that the IP address of the current sys_peer is 213.222.11.222 
(which is what gets output in binary as the refid).

One more data point: here is the output of 'ntpq -p -c rv localhost' 
which ntptrace turned into the above output:

assID=0 status=06f4 leap_none, sync_ntp, 15 events, event_peer/strat_chg,
version="ntpd 4.2.2p1 at 1.1570-o Sun Jul  9 11:18:35 UTC 2006 (1)",
processor="i686", system="Linux/2.4.20-28.7", leap=00, stratum=1,
precision=-20, rootdelay=0.000, rootdispersion=451.539, peer=63864,
refid=ÕÞ
         Þ, reftime=c870ad28.383ed848  Tue, Jul 25 2006 16:46:00.219,
poll=10, clock=c870ae8d.6d58d599  Tue, Jul 25 2006 16:51:57.427,
state=4, offset=0.497, frequency=6.306, jitter=3.058, noise=2.836,
stability=0.003, tai=0

So: this problem is not caused by ntptrace; the incorrect refid, stratum 
etc. are already shown by the ntpq -n -c rv output.

Hope this helps.

Jan




More information about the questions mailing list