Bug 6899

Summary: xntpd screams verbosely about down peers/servers
Product: [Retired] Red Hat Linux Reporter: Chris Siebenmann <cks-rhbugzilla>
Component: xntp3Assignee: Preston Brown <pbrown>
Severity: low Docs Contact:
Priority: medium    
Version: 6.1   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-01-19 21:12:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Chris Siebenmann 1999-11-10 22:43:29 UTC
If you are peering with a machine that goes down, or that
stops running an NTP daemon, you will see screams in your
syslog of the form:
	xntpd[26005]: recvfrom() fd=7: Connection refused
Worse, these are logged with priority LOG_ERR, which is
supposed to mark fairly important problems.

 These exist because Linux + glibc return errors on
recvfrom() that are due to a previous UDP sendto() on
the same socket failing because of various detectable
problems. The xntp3 code is not expecting this to
happen, and thinks that these are real recvfrom()

 These syslog messages are annoying. I've developed a
patch to muzzle them for connection refused, host down,
and host/net unreachables, if people are interested.

Comment 1 Jeff Johnson 1999-11-10 22:48:59 UTC
Could you reply to this message with patch attached? Thanks ...

Comment 2 Preston Brown 2001-02-01 17:38:06 UTC
closed due to lack of additional feedback, and the fact that this is solved with
newer versions in currently available distributions of Red Hat Linux.