I have a few Debian XEN virtual machines and upgraded them to wheezy(I need the 3.2 kernel for a project). Everything was okay until I rebooted on of the machines.
My current problem is, that ntpdate sets a wrong date after booting, which has severe implications on the application that is running on the VMs(crashes, currupt data, etc. - time is important on those servers).
Shortly after boot I ran the ntpdate command two times - with the following (confusing) output:
$> ntpdate server1 server2 server3
9 Apr 20:42:26 ntpdate[2371]: step time server x.x.x.x offset 83.293954 sec
$> ntpdate server1 server2 server3
9 Apr 20:40:45 ntpdate[1800]: step time server x.x.x.x offset -83.294240 sec
After those two executions, ntpdate works just as always, returning offsets less than .0001 seconds.
This problem is the same on all VMs in the cluster, just that the time offset differs. I have seen a server syncing ~2800 seconds like this, so the 83 seconds in the sample above are pretty low values.
Is there any way to tell why ntpdate is setting the time forward and shortly afterwards backward again?!
Edit: The time on Dom0 is correct and also synced.