Bug 1260140
Summary: | ntpdate -u -q -p 2 clock.redhat.com takes almost 3.5 times longer in RHEL 7 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Bryan Totty <btotty> |
Component: | ntp | Assignee: | Miroslav Lichvar <mlichvar> |
Status: | CLOSED NOTABUG | QA Contact: | qe-baseos-daemons |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | bwelterl, mlichvar, mvanderw |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-29 07:59:06 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
Bryan Totty
2015-09-04 14:11:35 UTC
This is the standard behavior of ntpdate since 4.2.6. The 2s spacing between packets was added to avoid a rapid burst which can trigger the KoD RATE response on the server. NTP clients are not supposed to use such short polling intervals. In the RHEL6 ntp rebase to 4.2.6 the original behavior of ntpdate from 4.2.4 was restored in a patch to avoid problems as described in this bug report after minor RHEL updates, but I don't think the same should be done in the RHEL7 ntp. My suggestion would be to use -p 1 to send just one packet to each server. For monitoring purposes there shouldn't be any need to send more packets. Here is the original upstream bug report which requested increasing the ntpdate polling interval to 2 seconds: https://bugs.ntp.org/show_bug.cgi?id=1504 Some comments about the new ntpdate behavior: https://bugs.ntp.org/show_bug.cgi?id=1853 |