Bug 82340 - NTP does not query the time server frequently enough to prevent drift
NTP does not query the time server frequently enough to prevent drift
Product: Red Hat Linux
Classification: Retired
Component: ntp (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-01-21 09:33 EST by Michael Lee Yohe
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-21 11:59:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Lee Yohe 2003-01-21 09:33:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030102

Description of problem:
My system generally gains two minutes in a week period.  This system has been
running non-stop for two weeks now, and was four minutes fast.  I have
configured NTP (using redhat-config-date) so that it would query the time server
for updates to keep the clock syncronized.  I have noticed that it had not
queried at all during the two week period.  Upon running redhat-config-date
again, it manually checked the time server and then corrected the time drift.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. see description

Actual Results:  Clock drifts fast...

Expected Results:  Clock should stay in sync with nightly queries to the time

Additional info:

$ rpm -q ntp
Comment 1 Harald Hoyer 2003-01-21 11:15:17 EST
what does ntpdc say?

# /usr/sbin/ntpdc
ntpdc> peers
     remote           local      st poll reach  delay   offset    disp
Comment 2 Michael Lee Yohe 2003-01-21 11:53:07 EST
$ /usr/sbin/ntpdc 
ntpdc> peers
     remote           local      st poll reach  delay   offset    disp
=time.nist.gov         16  512    0 0.00000  0.000000 0.00000
Comment 3 Harald Hoyer 2003-01-21 11:59:13 EST
so it does not connect... your /etc/ntp.conf should look like:

restrict default ignore
restrict mask nomodify notrap noquery
driftfile /etc/ntp/drift
broadcastdelay 0.008
authenticate yes
keys /etc/ntp/keys
Comment 4 Michael Lee Yohe 2003-01-21 12:09:05 EST
Okay - then perhaps this bug needs to be Component == redhat-config-date.  When
I configured ntp at installation, I expected it to query the server once in a
while.  This default configuration apparently does not query the server due to
an initial configuration issue.

The period by which an update can be made should be configurable by

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