Bug 32659
Summary: | ntpdate fails to operate, issues false error msg | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Neal Pollack <neal> |
Component: | ntp | Assignee: | Preston Brown <pbrown> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | jakub |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-03-26 15:46:57 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Neal Pollack
2001-03-22 06:33:36 UTC
reproducible in our test lab against public ntp servers, and I can't find an explanation in the package documentation. I have noticed on previous versions and systems that port 123 MUST be open for return traffic, else NTP will fail. Could this be a case where default security on Wolverine with 2.4 kernel and iptables is blocking this port by default? I am going to try to investigate the deafult security settings tonight. Possibly, yes. Network configuration of the test machine can be the source of my error as well, will confirm with a different network config. This seems to be a glibc issue. 4.0.99k (the 7.0 version) works fine on 7.0, but is broken on Wolverine and rawhide, with glibc 2.2.2-7 at least. further investigation indicates this to be a firewall issue. "Medium" and "High" security firewall settings in the betas/rawhide will result in the return port for ntpdate being closed off, thuse the error. Your firewall will have to be adjusted (partially opened) to allow ntpdate to operate properly. |