Ok. I’ve got ntp configured and running on my OpenSuSE 11.1 box. However, the clock is 7 minutes off (slow) [1]. At first, I was just using the ntp server that Yast wrote to the config file, “bigben.cac.washington.edu” . Then, thinking that, unlikely as it seemed, perhaps the server at bigben was incorrect, so I switched to the north-america pool servers: 0.north-america.pool.ntp.org, 1.north-america.pool.ntp.org, 2.north-america.pool.ntp.org and 3.north-america.pool.ntp.org and restarted the ntp daemon. No change.
Any suggestions where to look?
[1] As compared to my cellphone and the time announced on the news.
Also keep in mind that unless you slam your time (the service usually
does this when it first starts) to the correct time NTP is made to drift
back to correct time slowly. To slam the time manually (to see if it
will stay in sync) run:
Also, regarding the firewall, there is no reason to change the firewall
at all for a machine to be an NTP client as it is an outgoing connection
and not something coming into the server.
Finally you may want to delete the ntp.drift file which is probably in
/var/lib/ntp/drift (guessing) if it exists and has a non-zero value in
it in case that is throwing things off before they start adjusting properly.
Good luck.
Malcolm wrote:
>
> Hi
> It may still be using the local clock, in the ntp YaST setting make
> sure you have selected a few servers (I use 3)
>
> Also check via the command line;
>
> sudo ntpq
> ntpq> peers
>
> The active one should have a * by the name. Did you open the firewall
> port?
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
That appears to be what was happening here. I came back to the computer an hour or so after posting my original message and the clock was in sync. Not sure why changing from the bigben server at UW would change things (it’d been set to that for a week or so before hand), but changing the servers and restarting the service appears to have, eventually, had the desired result.
Thanks for the ideas, now I’ve got a little more to poke at if I run into problems in the future.
Also keep in mind that the GUI clock isn’t necessarily perfectly
synchronized with the system clock. Always use date to check time
just in case.
Good luck.
baronmog wrote:
> ab@novell.com;1930803 Wrote:
>> Also keep in mind that unless you slam your time (the service usually
>> does this when it first starts) to the correct time NTP is made to drift
>> back to correct time slowly.
>>
>
> That appears to be what was happening here. I came back to the computer
> an hour or so after posting my original message and the clock was in
> sync. Not sure why changing from the bigben server at UW would change
> things (it’d been set to that for a week or so before hand), but
> changing the servers and restarting the service appears to have,
> eventually, had the desired result.
>
> Thanks for the ideas, now I’ve got a little more to poke at if I run
> into problems in the future.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org