[ntp:questions] Inconsistency between ntptrace and ntpq?

Jan Ceuleers janspam.ceuleers at computer.org
Mon Jan 3 15:10:20 UTC 2005


All,

I am running ntpd 4.2.0a at 1.1190-r under RedHat Linux 7.2 (kernel
2.4.20-28.7).

I have noticed that on occasion there is a considerable time lag
between the  synchronisation source as reported by ntptrace and that
reported by ntpq -p localhost.

Below is the output from a simple script called ntpStatus, which
contains the following commands:

#!/bin/sh
cat /etc/ntp/drift
ntptrace
ntpq -p localhost

[root at penta root]# ntpStatus
5.911
penta: stratum 1, offset -0.002305, synch distance 0.457227, refid
'DCFa'
     remote           refid      st t when poll reach   delay   offset
jitter
==============================================================================
 LOCAL(0)        LOCAL(0)        10 l   33   64  377    0.000    0.000
0.001
 GENERIC(0)      .DCFa.           0 l    -   64    0    0.000    0.000
4000.00
*remco.tk        .PG0A.           1 -  941 1024  377   25.857    0.387
0.325
+hendrek.colo.fr 192.36.134.25    2 -  942 1024  377   30.131   -4.743
1.276
xgw.roaima.co.uk 212.159.13.50    3 -  932 1024  377  181.769   52.771
41.212
-ns2.medbanner.c 192.43.244.18    2 -  889 1024  377  125.848   -8.648
0.057
-ntp1.belbone.be 195.13.23.250    2 -  905 1024  377   14.155  -25.654
0.844
+time.ijs.si     193.2.4.2        3 -  901 1024  377   58.581    0.796
0.144

As you can see ntptrace thinks that the local DCF refclock is the
timing source that is currently believed, whereas according to the
ntpq output the DCF refclock has not been providing timing data for
quite a while (reach=0) and it is the remco.tk server that is
currently syncing the system.

Any ideas why this may be so?

Best wishes,

Jan



More information about the questions mailing list