Ah, a very important detail that I forgot to include : It's a Xen VM.
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 :
Code:
[root@bugzilla ~]# hwclock --show
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
As well as in other hardware machines I had. I decided to check in the host machine, and it also had a big skew. This time ntpdate worked as expected and ntpd running and active in chkconfig will keep things working in the long run.
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 :
Code:
[root@bugzilla ~]# ntpdate 131.215.145.254
20 Feb 11:12:54 ntpdate[2474]: adjust time server 131.215.145.254 offset -0.004173 sec
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. Bottom line is that solving the issue in the host and rebooting the VM helped.
Thanks!