Time oddities
Two oddities:
My brand new linode (woohoo!) is 2 seconds fast as determined by other independent ntp controlled systems (my home machine - sync'd to Verizon's NTP - and my work machine - sync'd to a GPS - which agree on the time)
The "process queue" web page has a datestamp that is approx 50 seconds fast.
4 Replies
I believe Linux doesn't sync itself with the hardware clock except at bootup, and when ntpd connects to a time server. So if your linode has been up for awhile w/o sync'ing itself via ntpd service perhaps that would cause a disparency in time.
@sweh:
My brand new linode (woohoo!) is 2 seconds fast as determined by other independent ntp controlled systems (my home machine - sync'd to Verizon's NTP - and my work machine - sync'd to a GPS - which agree on the time)
The hosts are using NTP, and as far as I can tell, all of them are synced correctly. Is this just a difference between your timesource and mine?
@sweh:
The "process queue" web page has a datestamp that is approx 50 seconds fast.
This doesn't suprise me – the webserver box goes out of sync every now and then. I'll try to get ntpd running on it as well.
Thanks!
-Chris
@caker:
The hosts are using NTP, and as far as I can tell, all of them are synced correctly. Is this just a difference between your timesource and mine?
I checked against two independent timesources; they agreed with each other, but my linode differed. I've just rechecked and now the linode is matching my other sources. Maybe the host was settling down? Dunno. At least it's right now
@caker:
This doesn't suprise me – the webserver box goes out of sync every now and then. I'll try to get ntpd running on it as well.
That'd be great