[ntp:questions] Re: ntp server 'rejected'

david.sanderson at bem.fki-et.com david.sanderson at bem.fki-et.com
Wed Apr 19 14:26:54 UTC 2006


>> The servers diagnostics indicate it is happy, and I can sync a linux
>> (Fedora core 4) box to it ok.


>Interesting, perhaps a client version difference: what does "ntpq -crv"
>show on your QNX box and your Linux box?

The linux box shows:

ntpq> lpe
     remote           refid      st t when poll reach   delay   offset
jitter
==============================================================================
 LOCAL(0)        LOCAL(0)        10 l   32   64  377    0.000    0.000
 0.004
*172.16.151.4    .GPS.            1 u  354 1024  377    1.467    1.698
 0.004


ntpq> as

ind assID status  conf reach auth condition  last_event cnt
===========================================================
  1 53012  9014   yes   yes  none    reject   reachable  1
  2 53013  9614   yes   yes  none  sys.peer   reachable  1


ntpq> rv 53013
assID=53013 status=9614 reach, conf, sel_sys.peer, 1 event,
event_reach,
srcadr=172.16.151.4, srcport=123, dstadr=172.16.20.117, dstport=123,
leap=00, stratum=1, precision=-20, rootdelay=0.000,
rootdispersion=996.750, refid=GPS, reach=377, unreach=0, hmode=3,
pmode=4, hpoll=10, ppoll=10, flash=00 ok, keyid=0, ttl=0, offset=1.698,
delay=1.467, dispersion=14.844, jitter=0.004,
reftime=c7f0bd31.269da597  Wed, Apr 19 2006 14:44:17.150,
org=c7f0bd3a.a7a0945f  Wed, Apr 19 2006 14:44:26.654,
rec=c7f0bd3a.a7616723  Wed, Apr 19 2006 14:44:26.653,
xmt=c7f0bd3a.a6fdfc19  Wed, Apr 19 2006 14:44:26.652,
filtdelay=     1.47    1.52    1.48    1.51    1.58    1.55    1.51
1.46,
filtoffset=    1.70    1.70    1.74    1.61    1.65    1.63    1.66
1.73,
filtdisp=      0.00   15.39   30.77   46.13   61.49   76.86   92.24
107.61
ntpq>



>I gather your stratum-1 has two interfaces; have you tried the QNX
>client with only one of the server's addresses configured?

Yes, I have tried each single port through a network, and a crossover.
both of them exhibit the same 'feature'


<<SNIP>>



>> ntpq> rv
>> status=09f4 leap_none, sync_telephone, 15 events, event_peer/strat_chg,
>> ntpq> version="ntpd 4... at 1.1161-r Mon Oct 25 15:22:31 BST 2004 (14)",
>> processor="i686", system="Linux/2.4.20-8", leap=00, stratum=1,
>> precision=-20, rootdelay=0.000, rootdispersion=996.710, peer=21093,
>> refid=GPS, reftime=c7e9cb1a.66643cc0  Fri, Apr 14 2006  7:17:46.399,
>> poll=4, clock=c7e9cb25.2c766c6d  Fri, Apr 14 2006  7:17:57.173,
>> state=4,
>> offset=-0.001, frequency=-4.862, jitter=0.006, stability=0.000

>> I can see nothing suspicious here, apart from sync_telephone possibly?

>That, and there's the rootdispersion again.  What does "ntpq -crv 21093"
>show?  (adjust for current peer assoc id).

This is on the NTP Server:

ntpq> rv 21093
status=96f4 reach, conf, sel_sys.peer, 15 events, event_reach,
ntpq> srcadr=SHM(1), srcport=123, dstadr=127.0.0.1, dstport=123,
leap=00,
stratum=0, precision=1700881256, rootdelay=0.000, rootdispersion=0.000,
refid=GPS, reach=377, unreach=0, hmode=3, pmode=4, hpoll=4, ppoll=4,
flash=00 ok, keyid=0, ttl=0, offset=0.001, delay=0.000,
dispersion=996.348, jitter=0.002,
reftime=c7f0c2e1.ffffeed9  Wed, Apr 19 2006 14:08:33.999,
org=c7f0c2e1.ffffeed9  Wed, Apr 19 2006 14:08:33.999,
rec=c7f0c2e2.24c8cd63  Wed, Apr 19 2006 14:08:34.143,
xmt=c7f0c2e2.24c79f66  Wed, Apr 19 2006 14:08:34.143,
filtdelay=     0.00    0.00    0.00    0.00    0.00    0.00    0.00
0.00,
filtoffset=    0.00    0.00    0.00    0.00    0.00    0.00    0.00
0.00,
filtdisp=   1000.00 1000.27 1000.53 1000.80 1001.04 1001.28 1001.52
1001.76

ntpq>

Is this just the dispersion forn the GPS source? It doesnt have a very
good view
of the sky, but the diagnostics claim all is healthy and ok, and the
Linux box
isnt complaining...

>What is your GPS clock?  Is this a Galleon NTP server, by any chance?
>I see similar behaviour with what I have been told is one of those,
>from an ntp-4.0.99k client.

It is a Galleon NTP Server. The QNX claims:
version="ntpd 4.1.1 at 1.786 Thu Mar 27 11:18:57 EST 2003 (3)" in its rv.
but the linux is much newer:
version="ntpd 4.2.0a at 1.1190-r Thu Apr 14 07:47:25 EDT 2005 (1)"


Interestingly I have an x86 based QNX box which seems to sync and then
lose sync periodically. An extract from its ntplog.txt:

19 Apr 01:56:34 ntpd[712743]: offset -0.000258 sec freq -28.507 ppm
error 0.000590 poll 10
19 Apr 02:46:34 ntpd[712743]: synchronisation lost
19 Apr 02:56:34 ntpd[712743]: offset 0.000135 sec freq -28.501 ppm
error 0.000548 poll 4
19 Apr 03:56:34 ntpd[712743]: offset -0.001126 sec freq -28.522 ppm
error 0.000490 poll 9
19 Apr 04:56:34 ntpd[712743]: offset -0.000500 sec freq -28.518 ppm
error 0.000502 poll 10
19 Apr 05:56:34 ntpd[712743]: offset 0.000274 sec freq -28.507 ppm
error 0.000493 poll 10
19 Apr 06:56:34 ntpd[712743]: offset -0.000152 sec freq -28.513 ppm
error 0.000565 poll 10
19 Apr 07:56:34 ntpd[712743]: offset -0.000387 sec freq -28.516 ppm
error 0.000653 poll 10
19 Apr 08:56:34 ntpd[712743]: offset 0.000184 sec freq -28.508 ppm
error 0.000564 poll 10
19 Apr 09:56:34 ntpd[712743]: offset -0.000261 sec freq -28.514 ppm
error 0.000605 poll 10
19 Apr 10:56:34 ntpd[712743]: offset 0.000227 sec freq -28.507 ppm
error 0.000541 poll 10
19 Apr 11:00:54 ntpd[712743]: synchronisation lost
19 Apr 11:56:33 ntpd[712743]: offset -0.000805 sec freq -28.515 ppm
error 0.000493 poll 9

where as the XScale box log looks like:

19 Apr 11:35:26 ntpd[335884]: offset 0.000000 sec freq 0.000 ppm error
0.000488 poll 4
19 Apr 12:35:26 ntpd[335884]: offset 0.000000 sec freq 0.000 ppm error
0.000488 poll 4
19 Apr 13:35:26 ntpd[335884]: offset 0.000000 sec freq 0.000 ppm error
0.000488 poll 4

I have also tried setting the x86 QNX box as the server for the XScale,
though this
wont be possible in the final setup, but just to see if it could be
persuaded to sync,
that didnt work either :( Im getting to Hair pulling stage now, and no
one at QNX
seems to be home either!

Thanks for the continuing help

Dave




More information about the questions mailing list