CentOS - Aug 2012 - C6: ntpd time reset +277092510.162464 s

Hi,

I'm in the middle of migrating our oracle servers to RHEL and C6;
while testing ntpd I'm seeing time resets.

I see in sysconfig/ntpd the option g is set which means huge offset is 
one time ignored.  But my understanding of ntpd is, it slows or 
accelerated kernel clock but does not make huge jumps...

Is this really expected behaviour?

The file step-tickers is empty, ntp.conf is minimal:

driftfile /var/lib/ntp/drift
restrict default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer noquery
restrict 127.0.0.1
restrict -6 ::1
server 10.0.1.27

/var/log/messages:

Nov 20 12:48:06 aitcsdb002 ntpd[5816]: ntpd 4.2.4p8 at 1.1612-o Thu May 13 
14:38:25 UTC 2010 (1)
Nov 20 12:48:06 aitcsdb002 ntpd[5817]: precision = 0.065 usec
Nov 20 12:48:06 aitcsdb002 ntpd[5817]: Listening on interface #0 
wildcard, 0.0.0.0#123 Disabled
Nov 20 12:48:06 aitcsdb002 ntpd[5817]: Listening on interface #1 
wildcard, ::#123 Disabled
Nov 20 12:48:06 aitcsdb002 ntpd[5817]: Listening on interface #2 lo, 
::1#123 Enabled
Nov 20 12:48:06 aitcsdb002 ntpd[5817]: Listening on interface #3 eth1, 
fe80::20c:29ff:fef1:3fee#123 Enabled
Nov 20 12:48:06 aitcsdb002 ntpd[5817]: Listening on interface #4 eth0, 
fe80::20c:29ff:fef1:3fe4#123 Enabled
Nov 20 12:48:06 aitcsdb002 ntpd[5817]: Listening on interface #5 lo, 
127.0.0.1#123 Enabled
Nov 20 12:48:06 aitcsdb002 ntpd[5817]: Listening on interface #6 eth0, 
10.0.4.16#123 Enabled
Nov 20 12:48:06 aitcsdb002 ntpd[5817]: Listening on interface #7 eth1, 
10.0.5.16#123 Enabled
Nov 20 12:48:06 aitcsdb002 ntpd[5817]: Listening on routing socket on fd 
#24 for interface updates
Nov 20 12:48:06 aitcsdb002 ntpd[5817]: kernel time sync status 2040
Aug 31 16:00:51 aitcsdb002 ntpd[5817]: synchronized to 10.0.1.27, stratum 3
Aug 31 16:00:51 aitcsdb002 ntpd[5817]: time reset +277092510.162464 s

Thx

On 31/08/12 15:09, Rainer Traut wrote:
> I see in sysconfig/ntpd the option g is set which means huge offset is 
> one time ignored.  But my understanding of ntpd is, it slows or 
> accelerated kernel clock but does not make huge jumps...
With the options you mentioned, NTPd will make a big jump once at startup.

If the clock is wrong by (if I remember correctly) about 30 mins it will
take so long to drift back to being correct that NTPd gives up.

On Fri, Aug 31, 2012 at 04:09:54PM +0200, Rainer Traut
wrote:
> Hi,
> 
> I'm in the middle of migrating our oracle servers to RHEL and C6;
> while testing ntpd I'm seeing time resets.
Well, the delta-T is something like 8.8 ~years~, so I'd suggest
first checking the BIOS clock in the host in question, and if it
is always so far from truth, replace its little battery.

Dave
-- 
                     If you see something, keep quiet.