Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 77086 - Unable to sync system time
Unable to sync system time
Product: Red Hat Linux
Classification: Retired
Component: ntp (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2002-10-31 17:43 EST by Milan Kerslager
Modified: 2007-04-18 12:48 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-14 16:02:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2002:230 normal SHIPPED_LIVE New ntp package fixes a bug in parsing command line options 2002-10-10 00:00:00 EDT

  None (edit)
Description Milan Kerslager 2002-10-31 17:43:10 EST
I'm unable to use ntpdate to sync time&date because too big offset:

# ntpdate tak.cesnet.cz
 2 Nov 01:36:50 ntpdate[1581]: Can't adjust the time of day: Invalid argument
# ntptrace tak.cesnet.cz
tak.cesnet.cz: stratum 1, offset -93634.278879, synch distance 0.00157, refid 'GPS'
# date 10312339
# ntpdate tak.cesnet.cz
31 Oct 23:39:11 ntpdate[1588]: step time server offset 6.853757 sec

Seems odd error message or stupid bug... I don not remember same problem with
old version of ntpdate (without libcap) but I could be wrong (I did not tested it).
Comment 1 John I Wang 2002-11-08 11:13:49 EST
I've noticed this problem with the RedHat 8.0 distribution.   It's not a problem
with ntp but a problem with dhcpcd.   Apparently, it fails to make the entry:
   restrict NTP-SERVER
in the /etc/ntp.conf file (where NTP-SERVER is the ip-address or name provided
via DHCP).   Since it does make the entry:
   restrict default ignore
the end result is that ntp is effectively blocked from syncing with anyone.

I was about to submit it as a dhcpc bug but decided to check the ntp bugs to see
if someone else had encountered the issue.
Comment 2 Milan Kerslager 2002-11-11 08:59:44 EST
Seems to be two different bugs. I had no ntp daemon running and I did not used
dhcpd to obtain IP address. I'm only using ntpdate to sync time every hour
(because ntp daemon was not so fail-proof).

What I did is try to use with ntpdate to change local time and it refused to do
because "bad argument". This is odd. The second problem is that script for ntpd
daemon is using ntpdate to sync time like I did, but this simply not work when
time offset is too big as I reported.

I'm reopening to point that there is an inconsistency.
Comment 3 Harald Hoyer 2002-11-11 10:58:10 EST
ok, found the bug in the source.. .thx for reporting...
Comment 4 Tim Coote 2002-12-13 04:31:47 EST
I had problems with ntp that relate to the default ignore entry in the 
ntp.conf. they didn't come from dhcp, I think it's just the defaul entry in 
the config file.

- ntp doesn't log that it's not synching. in fact there's no indication that 
anything's wrong unless you happen to do a manual clock check
- there's no warning from ntp that it's got a stupid configuration. in fact 
it's not trivial to find that it's getting the returned signals correctly and 
then throwing them away. (I faffed for ages checking firewall settings, and 
ethereal to be sure that something was going on at all.
Comment 5 Harald Hoyer 2003-01-09 10:25:51 EST
should be fixed with ntp-4.1.1b-1
Comment 6 John Flanagan 2003-02-14 16:02:09 EST
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


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