ntpdate not updating system time in XenServer VM
Solution 1
I have been through this before.
Try (on domU):
echo 1 > /proc/sys/xen/independent_wallclock
and try updating the time again.
Solution 2
Try by this procedure:
Stop the ntpd service first:
service ntpd stop
Now update the local time
ntpdate "server name"
and after this start the service:
service ntdp start
Solution 3
Try running ntpdate on an unprivileged port (in case you are running ntpd), otherwise it will refuse make any changes.
ntpdate -u ntp0.cs.mu.oz.au
Solution 4
Did the time change when you set the new time using date?
Try and check the machine hardware clock. (man hwclock)
Related videos on Youtube
Comments
-
LukeR over 1 year
We have a Debian webserver that I am trying to use ntpdate to keep the time in sync.
When I run
ntpdate ntp0.cs.mu.oz.au
I receive
16 Sep 10:55:36 ntpdate[21626]: step time server 128.250.36.2 offset 318.914011 sec
With no errors, which should be a good thing, I think...
When I check the time again though, it's not changed.
I am also unable to set the time manually using
date --set 11:00:00
So I have a feeling there are other issues.
Any advice would be appreciated.
Update
Sorry for the bum steer guys, this machine is a XenServer VM, which I managed to forget.
After updating the Host clock, the VM time is now correct.
Thanks for your replies. Thanks.
-
Admin over 14 yearsNot related to the original request, but... note that ntp0.cs.mu.oz.au has now been discontinued and stopped responding to queries. I suggest using au.pool.ntp.org instead.
-
-
Kyle Brandt over 14 yearsWith date are you running it as root?
-
LukeR over 14 yearsyep, eveything is run as root.
-
LukeR over 14 yearsHow long should it take? It doesn't appear to have changed in the last .5 hour. I'm still seeing the same offset 318.9... secs
-
LukeR over 14 yearsno. I am unable to set the date with either ntpdate or date
-
LukeR over 14 yearsno dice. still no changes