Ntpdate not updating time
20 Feb ntpdate: step time server 18.104.22.168 offset -2770.341672 sec [[email protected] ~]# ntpdate 22.214.171.124 20 Feb ntpdate: step time server 126.96.36.199 offset -2770.341754 sec [[email protected] ~]# ntpdate 0.20 Feb ntpdate: step time server 1.202 offset -2770.345091 sec [[email protected] ~]# ntpdate 0.20 Feb ntpdate: step time server 1.202 offset -2770.345357 sec [[email protected] ~]# service ntpd status ntpd is stopped OBS:188.8.131.52 is the campus NTP server, disguised. Let me know if can give any clue, ommited it to not send a lot of junk to the thread at first.But as you see, not even the official Cent OS servers help. Thanks, Samir Ah, a very important detail that I forgot to include : It's a Xen VM.Ping (and traceroute) are simply there to debug IP-level connectivity: they do nothing to test transport-level (TCP, UDP) service availability / reachability.Visit Stack Exchange In my case I was running a Ubuntu on a virtualbox and had saved the machine state so when I started the instance back up again it did not automatically sync the clock since there was no boot event to trigger the sync.Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
But you should usually specify the country you want the servers to be from by using the country code in the hostnames.Then as the VM would stay stuck in the same bad skew, I tried rebooting it to see if it would restore it to a decent state.It did, after reboot ntpd got the right date and ntpdate showed a small skew : That solves my problem, it's a pity that I didn't manage to find the reason to share here for people with the same problem in the future.I also heard of Xen VMs clocks misbehaving before, but not like that and nothing that ntpd running wouldn't solve.
Thanks for the idea hwclock gave me an error : As well as in other hardware machines I had.
If "ntpdate" does not work, it means that something is blocking NTP packets.