Vmware ESXi (3.5) and RHEL (5.1) : Timekeeping Woes

John Hodrien J.H.Hodrien at leeds.ac.uk
Tue Sep 15 07:11:59 CDT 2009


On Tue, 15 Sep 2009, Brian O'Mahony wrote:

> I may have posted this here previously, and if not I know I spoke to Dell
> support, whom advised me to make sure that the “Synchronize guest time with
> host” was turned off.
>
> Basically I have a RHEL5.1 server. It has the ntpd service running. This
> seems to stop every now and again. It took me quite some time to organize
> downtime on this VM, so I only got to turn off the option in setting last
> week.
>
> Here is the log from messages:
>
> messages:Sep 13 10:28:07 curzilla ntpd[2593]: synchronized to LOCAL(0), stratum 10
> messages:Sep 13 11:35:50 curzilla ntpd[2593]: synchronized to 172.16.164.100, stratum 4
> messages:Sep 13 15:18:10 curzilla ntpd[2593]: synchronized to LOCAL(0), stratum 10
> messages:Sep 13 19:33:29 curzilla ntpd[2593]: synchronized to 172.16.164.100, stratum 4
> messages:Sep 14 08:04:52 curzilla ntpd[2593]: synchronized to LOCAL(0), stratum 10
> messages:Sep 14 09:30:14 curzilla ntpd[2593]: synchronized to 172.16.164.100, stratum 4
> messages:Sep 14 22:01:36 curzilla ntpd[2593]: synchronized to LOCAL(0), stratum 10
> messages:Sep 15 01:10:27 curzilla ntpd[2593]: synchronized to 172.16.164.100, stratum 4
> messages:Sep 15 01:26:28 curzilla ntpd[2593]: time correction of 2232 seconds exceeds sanity limit (1000); set clock manually to the
> correct UTC time.
>
>
>
> Anyone have any ideas/suggestions?

It stops because you clock goes out of all reasonable bounds of wrongness, and
ntp decides to not trust the ntp server as it's too far out.  You could just
remove that restriction in ntp.conf:

tinker panic 0

That way, ntp will always trust network time over local time.  Still means
you've got local time keeping problems, but ntp will keep dragging it back to
correct.

jh


More information about the Linux-PowerEdge mailing list