<HTML>
<HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<font size="2"><b>---------- Original Message
-----------</b>
<br />
From: Michael Stauber <mstauber@blueonyx.it>
<br />
To: BlueOnyx General Mailing List <blueonyx@mail.blueonyx.it>
<br />
Sent: Tue, 10 Jun 2014 21:37:04 -0500
<br />
Subject: [BlueOnyx:15529] Re: Problem with server clock intermittenly changing
<br />
<br />> Hi Chuck,
<br />>
<br />>
> I've got a weird one. The clock on just one of our BX servers keeps
changing.
<br />>
> This morning at 08:45 - the clock set backwards 12 hours to 9June 21:03.
Then
<br />>
> less than two hours later - it sets back forward to the correct time.
See cron
<br />>
> log clips below.
<br />>
>
<br />>
> I'd previously turned off NTPd, since it wasn't keeping the time right and
had
<br />>
> set up a daily cron to set the clock. But the problem has remained -
whether
<br />>
> using NTPd or the cron.
<br />>
>
<br />>
> Does anyone have a idea what could be changing the clock on this server?
<br />>
<br />>
Hmm. Could be that the timezone set in CODB disagrees with the TZ that
<br />>
the server is currently using. In that case a cronjob (or CCED restart)
<br />>
could push out the CODB stored timezone to the system. In which case
<br />>
you'd see such a jump.
<br />>
<br />>
Other than that: Updates of the "tzdata" RPM via YUM can also cause
this
<br />>
temporarily, until a CCED restart fixes it again.
<br />>
<br />>
Other than that? No idea. If you can't use NTP, then a cronjob is indeed
<br />>
the answer.
<br />>
<br />>
Once upon a time I used to use a cronjob like this to sync the software-
<br />>
and hardware-clock once a day:
<br />>
<br />>
5 23 * * * /usr/sbin/ntpdate -v time.fu-berlin.de
<br />>
6 23 * * * /sbin/clock -wu
<br />>
<br />>
--
<br />>
With best regards
<br />>
<br />>
Michael Stauber
<br />
<br />Thanks for the suggestions Michael.
<br />
<br />I'll try changing the timezone in the GUI two or three times, ending with the correct timezone. Maybe that will straighten out any CODB mis-match.
<br />
<br />I already have a cron that sets the time via ntpdate once a hour. But I wasn't pushing that down to the "hardware". Mainly because this one is a VM, and I've noticed timing issues whether NTPd was running or not. But I'll give that a try too, maybe it will help.
<br />
<br />Thanks again Michael. And I'll let you know if we have any further cases of time jumps in the logs.
<br />
<br />
<br />
<br />Chuck
<br />
<br />
<br />
</font>
</BODY>
</HTML>