[ntp:questions] Troubleshooting who's at fault

Miroslav Lichvar mlichvar at redhat.com
Thu Jun 25 18:05:12 UTC 2009


On Thu, Jun 25, 2009 at 10:17:52AM -0700, Ronaldo Mexico wrote:
> On Jun 25, 12:36 pm, Steve Kostecke <koste... at ntp.org> wrote:
> > On 2009-06-25, Ronaldo Mexico <ronaldo.hawk.mex... at gmail.com> wrote:
> >
> > > ntpq> rv 62340
> > > assID=62340 status=9014 reach, conf, 1 event, event_reach,
> > > srcadr=ntp, srcport=123, dstadr=147.159.120.206, dstport=123, leap=00,
> > > stratum=2, precision=-20, rootdelay=0.000, rootdispersion=0.000,
> > > refid=LOCAL(0), reach=377, unreach=0, hmode=3, pmode=4, hpoll=7,
> > > ppoll=7, flash=800 peer_loop, keyid=0, ttl=0, offset=-5.276,
> >
> > Note the "peer_loop". I'd check the configuration of the time server at
> > 147.159.120.206
> 
> Unfortunately, it's the RHEL server (147.159.120.206).  The PTS is on
> 147.159.120.131.  There are no other NTP servers in the private
> network.

I've seen a similar report. IIRC it was caused by server using refid INIT
in the replies which is interpreted in the client as a synchronization
loop. Check tcpdump output.

-- 
Miroslav Lichvar



More information about the questions mailing list