[ntp:questions] Fedora Core 5 NTP won't synchronize -- condition reject
dan.jakubiec at gmail.com
dan.jakubiec at gmail.com
Wed Jun 21 23:46:01 UTC 2006
I can't get my NTP client on my Fedora Core 5 box to synchronize. I
went through a number of the troubleshooting/FAQs I found, but I still
can't seem to make it go. Any help would be much appreciated.
I tried a number of different NTP servers (from the global pool, as
well as from my company's internal server). It appears that I am
sending and getting responses from the servers, but my NTP client is
rejecting them for some reason. Here is some pertinent output from my
ntpq:
ntpq> pe
remote refid st t when poll reach delay offset
jitter
==============================================================================
172.16.2.2 66.229.200.200 2 u 30 64 377 71.722 -6522.1
1638.79
ntpq> as
ind assID status conf reach auth condition last_event cnt
===========================================================
1 27340 9014 yes yes none reject reachable 1
ntpq> rv 27340
assID=27340 status=9014 reach, conf, 1 event, event_reach,
srcadr=172.16.2.2, srcport=123, dstadr=10.0.0.2, dstport=123, leap=01,
stratum=2, precision=-18, rootdelay=19.928, rootdispersion=70.419,
refid=66.229.200.200, reach=377, unreach=0, hmode=3, pmode=4, hpoll=6,
ppoll=6, flash=00 ok, keyid=0, ttl=0, offset=-6522.145, delay=71.722,
dispersion=2.130, jitter=1638.794,
reftime=c8444eb8.dd4ca925 Wed, Jun 21 2006 13:03:20.864,
org=c84456b0.9a19b90e Wed, Jun 21 2006 13:37:20.601,
rec=c84456b7.8e9728a6 Wed, Jun 21 2006 13:37:27.556,
xmt=c84456b7.7b0da5da Wed, Jun 21 2006 13:37:27.480,
filtdelay= 76.28 71.72 74.80 72.46 72.35 117.00 101.90
108.72,
filtoffset= -6916.9 -6522.1 -6123.9 -5652.6 -5168.1 -4737.3 -4291.7
-3740.8,
filtdisp= 0.01 1.00 1.96 2.95 3.91 4.85 5.80
6.79
ntpq> rv
assID=0 status=c011 sync_alarm, sync_unspec, 1 event, event_restart,
version="ntpd 4.2.0a at 1.1196-r Thu May 11 09:19:35 EDT 2006 (1)"?,
processor="i686", system="Linux/2.6.16-1.2133_FC5", leap=11,
stratum=16,
precision=-18, rootdelay=0.000, rootdispersion=15.150, peer=0,
refid=INIT, reftime=00000000.00000000 Wed, Feb 6 2036 20:28:16.000,
poll=6, clock=0xc84456de.27e93187, state=1, offset=0.000,
frequency=0.000, noise=0.004, jitter=0.004, stability=0.000
ntpq>
And from ntpc:
ntpdc> pstats 172.16.2.2
remote host: bigdog.systech.com
local interface: 10.0.0.2
time last received: 42s
time until next send: 24s
reachability change: 1400s
packets sent: 22
packets received: 22
bad authentication: 0
bogus origin: 0
duplicate: 0
bad dispersion: 0
bad reference time: 0
candidate order: 0
How can I find out why the NTP responses are being rejected? My system
log shows no errors, the "flash" variable is 0x00, I'm seeing the
responses on my Ethereal network capture, etc. I've also tried
removing all restrictions from my ntp.conf file. Any ideas from the
NTP gurus??
Thanks in advance,
--
Dan Jakubiec
More information about the questions
mailing list