ntp time 12 minutes slow
My Linux system shows a current time with the date command that is 12-14 minutes behind the time shown by my DirecTV satellite receiver or my wife's MS Vista system. ntpd is running; it's polling several ntp servers; ntpstat claims that the system time is accurate to 11ms. What could be going wrong?
|
Post the output of the command
ntpq -p |
Code:
# ntpq -p |
Basically none of the time servers are good enough to use (look at the values for offset and jitter) so ntp has defaulted to your local clock. Note the * beside LOCAL(0).
What does your /etc/ntp.conf file contain for servers? server 0.us.pool.ntp.org server 1.us.pool.ntp.org server 2.us.pool.ntp.org Offset is the difference between your clock and the server. Jitter is a measurement of stability of the timer server. Changing the clock within a couple of minutes will help sync your system to a ntp server faster. |
Quote:
Code:
server 0.fedora.pool.ntp.org |
BTW server 127.127.1.0 is a fake time server when your computer can not connect to the internet. Restarting ntpd was probably all that was needed. At least its working now.
|
Quote:
VMware and/or RedHat (can't remember right now), released a patch that supposedly fixed it. |
I do not think that VM servers are allowed in the ntp pool but I could be wrong.
|
I don't do anything that requires that sort of constant syncing. I just run "ntpdate time-b.nist.gov" every so often and that is good enough. I'm rarely more than five minutes off if I do that at least once a month. Baring any sort of power outage, heavy media processing / game playing, or other things that toys with the system clock. One caveat is that I do have to lower my network usage (dial-up connection) to have it work.
|
All times are GMT -5. The time now is 02:46 PM. |