[ntp:questions] Troubleshooting who's at fault

Steve Kostecke kostecke at ntp.org
Thu Jun 25 21:01:17 UTC 2009


On 2009-06-25, Ronaldo Mexico <ronaldo.hawk.mexico at gmail.com> 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).

Right ... I misread the billboard.

> The PTS is on 147.159.120.131. There are no other NTP servers in the
> private network.

You need to check the configuration of 147.159.120.131

Why is it synchronized to "LOCAL(0)"?

-- 
Steve Kostecke <kostecke at ntp.org>
NTP Public Services Project - http://support.ntp.org/




More information about the questions mailing list