Description of problem:
ntpd takes a long time (up to an hour) to synchronise with time servers. It
then loses synchronisation every 30 minutes or so. Before synchronisation is
lost "jitter" (as reported by ntpq pe command) starts to grow to 100s of
milliseconds. Replacing the supplied ntp rpm with the Red Hat 8.0 ntp rpm
fixes the problem (i.e. synchs within 3-4 minutes of starting and never loses
Version-Release number of selected component (if applicable):
Every time ntpd is started.
Steps to Reproduce:
1. Create simple ntp.conf, e.g.
2. /etc/init.d/ntpd start
3. Observe entries in /var/log/messages, e.g.
Mar 15 17:00:52 mallard ntpd: time reset 0.530494 s
Mar 15 17:00:52 mallard ntpd: synchronisation lost
Mar 15 17:18:25 mallard ntpd: time reset 0.858730 s
Mar 15 17:18:25 mallard ntpd: synchronisation lost
Mar 15 17:57:01 mallard ntpd: time reset -0.821846 s
Mar 15 17:57:01 mallard ntpd: synchronisation lost
Mar 15 18:16:41 mallard ntpd: time reset 0.667704 s
Mar 15 18:16:41 mallard ntpd: synchronisation lost
As above - synchronisation frequently lost. Time being set with .5 to 1 second
Synchronisation to be maintained and time to be maintained within a few
Just to add that I have tested this on a separate server running RHAS (same
ntpd rpm) with exactly the same results:
Mar 17 09:20:08 minx ntpd: time reset 0.770897 s
Mar 17 09:20:08 minx ntpd: kernel time discipline status change 1
Mar 17 09:20:08 minx ntpd: synchronisation lost
Mar 17 09:40:39 minx ntpd: time reset 0.305470 s
Mar 17 09:40:39 minx ntpd: synchronisation lost
This is when trying to sync to ntp servers in the same subnet.
can you try the latest rawhide version of ntp in your subnet? That would be my
candidate for a bugfix erratum.
Hi, I tried to install it but it requires glibc 2.3. Panama has glibc 2.2.4.
should be no problem to recompile the src.rpm
OK, compiled and installed the src.rpm and it works fine. Sync after about 3
minutes and no loss at all.
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.