Re: strange client behavior
- From: "R Jenkins" <not@xxxxxxxxxx>
- Date: Tue, 16 May 2006 15:42:33 +0100
"Aaron Bennett" <abennett@xxxxxxxxxx> wrote in message
news:4468F02A.7050507@xxxxxxxxxxxxx
Hello,Hi,
Here's a strange one for you all:
I have two clients with identical ntp.conf files:
restrict default nomodify notrap noquery
driftfile /var/lib/ntp/drift
broadcastdelay 0.008
server ntp.clarku.edu
restrict ntp.clarku.edu mask 255.255.255.255 nomodify notrap noquery
One of them, a Fedora Core 5 box running ntp-4.2.0.a.20050816-11, works
fine.
The other, a RHEL 4 AS box running ntp-4.2.0.a.20040617-4, seems to work
in that the clocks match, tcpdump shows udp traffic from the client to the
server on port 123, etc... _BUT_ ntpq -n -p fails after a few seconds with
this error:
[root@erebus ~]# ntpq -n -p
localhost.localdomain: timed out, nothing received
***Request timed out
[root@erebus ~]#
Any ideas? _______________________________________________
questions mailing list
questions@xxxxxxxxxxxxxxxxx
https://lists.ntp.isc.org/mailman/listinfo/questions
I've just had a very similar problem on my Centos 4.3 system, which uses
RHAS 4 source files.
It turned out to be a bug in the that 4.2.0a 2004 package.
I've rebuilt mine from the latest development sources, but you may be able
to use the RPM for Fedora 5, it looks to be a year newer.
Robert Jenkins.
.
- References:
- strange client behavior
- From: Aaron Bennett
- strange client behavior
- Prev by Date: Re: NMEA refclock - PPS not working
- Next by Date: Re: NMEA refclock - PPS not working
- Previous by thread: strange client behavior
- Next by thread: Book review of Mill's Computer Network Time Synchronization on slashdot
- Index(es):
Relevant Pages
|
Loading