Bug 1420628
Summary: | ntpd 4.2.2 select itself and sync failed intermittently,Is this a bug? | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | muahao <muahao> |
Component: | ntp | Assignee: | Miroslav Lichvar <mlichvar> |
Status: | CLOSED WONTFIX | QA Contact: | qe-baseos-daemons |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.7 | CC: | cww, muahao |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-04-04 20:27:57 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
muahao
2017-02-09 06:23:57 UTC
*** Bug 1420627 has been marked as a duplicate of this bug. *** Without seeing output from ntpq -c 'rv $ID', where ID is the association ID of the server from 'ntpq -c as' output, it's difficult to tell what exactly it's going on. However, as a general rule, it's not recommended to use the local driver (server 127.127.1.x) on NTP clients. It's meant to be used only on a server that should serve its local time when no other source is available. Can you please try removing the 127.127.1.0 lines from the configuration file? Please note that even if this is a bug in 4.2.2, it's very unlikely it will be fixed in RHEL6 as it's already in the production phase 2, where only critical bugs are now fixed. https://access.redhat.com/support/policy/updates/errata#Production_2_Phase Red Hat Enterprise Linux 5 shipped it's last minor release, 5.11, on September 14th, 2014. On March 31st, 2017 RHEL 5 exits Production Phase 3 and enters Extended Life Phase. For RHEL releases in the Extended Life Phase, Red Hat will provide limited ongoing technical support. No bug fixes, security fixes, hardware enablement or root-cause analysis will be available during this phase, and support will be provided on existing installations only. If the customer purchases the Extended Life-cycle Support (ELS), certain critical-impact security fixes and selected urgent priority bug fixes for the last minor release will be provided. For more details please consult the Red Hat Enterprise Linux Life Cycle Page: https://access.redhat.com/support/policy/updates/errata This BZ does not appear to meet ELS criteria so is being closed WONTFIX. If this BZ is critical for your environment and you have an Extended Life-cycle Support Add-on entitlement, please open a case in the Red Hat Customer Portal, https://access.redhat.com ,provide a thorough business justification and ask that the BZ be re-opened for consideration of an errata. Please note, only certain critical-impact security fixes and selected urgent priority bug fixes for the last minor release can be considered. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |