Bug 53350 - ntp logs bogus "Connection refused" messages
Summary: ntp logs bogus "Connection refused" messages
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: ntp
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-09-07 03:54 UTC by Jonathan Kamens
Modified: 2007-04-18 16:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-06-04 09:41:39 UTC
Embargoed:


Attachments (Terms of Use)

Description Jonathan Kamens 2001-09-07 03:54:01 UTC
I have five different servers listed in /etc/ntp.conf.  Recently, one of
them went off the air for a while.  However, although it was the only one
that was refusing NTP requests, while it was down I got log mesages
claiming that the *others* were, even though they weren't.

The host that was refusing connections was 66.92.64.2, but nothing was ever
logged about *that* host.  Instead, I got lots of these errors about the
*other* servers in my ntp.conf file, even though they were all working (as
confirmed by "dmpeers" in ntpdc:

Sep  4 00:24:26 jik ntpd[1043]: recvfrom(206.253.194.97) fd=6: Connection
refused
Sep  4 02:25:02 jik ntpd[1043]: recvfrom(216.231.41.22) fd=6: Connection
refused
Sep  4 02:29:19 jik ntpd[1043]: recvfrom(206.253.194.65) fd=6: Connection
refused
Sep  4 02:31:28 jik ntpd[1043]: recvfrom(18.72.0.144) fd=6: Connection
refused

Comment 1 Harald Hoyer 2001-12-14 13:28:42 UTC
should be fixed in ntp-4.1.0b-1


Comment 2 Harald Hoyer 2004-06-04 09:41:39 UTC
Closing due to inactivity. Reopen, if the problem is still existing.


Note You need to log in before you can comment on or make changes to this bug.