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

david.sanderson at bem.fki-et.com david.sanderson at bem.fki-et.com
Fri Apr 14 07:33:27 UTC 2006


>> jitter
>> ======================================================
>>  192.168.0.230   .GPS.            1 u   60   64  377    0.951  -105.64
>>  4.979
>>  172.16.151.4    .GPS.            1 u   52   64  377    0.953  -106.24
>>  5.051
>
>Something seems very wrong with the above!  Why do you have a 106
>millisecond offset?  It also appears that this box has not selected
>either of the available servers as a synchronization source!!

I have assumed the 106 ms offset comes from the clock drifting due to
it not being sync'd by ntp? I brute force set the clock with an ntpdate
before i started the ntpd, but from then it drifts...
It not selecting a server to sync is the probelm I think, but Im afraid
I have no idea why?

>> but the QNX box does not sync. The clock on the QNX box has about 80
>> ppm drift, as observed over a few days.
>> the Associations billboard :
>> # ntpq -c as
>> ind assID status  conf reach auth condition  last_event cnt
>> ===========================================================
>>   1     7  9014   yes   yes  none    reject   reachable  1
>>   2     8  9014   yes   yes  none    reject   reachable  1
>> So i can get to the server but it is being rejected. What does this
>> mean?

>It means that the server you are trying to synchronize with is not,
>itself, synchronized and therefore is not eligible to serve time!!

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

Ronan Flood wrote:
>Hmm, the rootdispersion looks suspect; but then I'd expect that to
>light one of the flash bits.  Can you look at the servers with ntpq?
>See maybe what "cl" and "rv" show on them?
Ok, I set the host to the clockbox:

ntpq> host 192.168.0.230
current host set to 192.168.0.230, I have a xover connection to one
port on this server, so 192. is not as bad as it seems.

ntpq> cl
status=0101 clk_noreply, last_clk_noreply,
ntpq> device="SHM/Shared memory interface", timecode=, poll=17039,
noreply=3671, badformat=0, baddata=0, fudgetime1=0.000, stratum=0,
refid=GPS, flags=0

there seem to be a lot of no replys?

ntpq> rv
status=09f4 leap_none, sync_telephone, 15 events, event_peer/strat_chg,
ntpq> version="ntpd 4.2.0 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?

Thanks for the help, this is an area I have not been in before.

Dave




More information about the questions mailing list