Chris Horn wrote: > cc: me on your reply, as I'm not subscribed)! > Running '/etc/init.d/ntpdate start' does not fix the problem. What do the logs say in /var/log/syslog? I suspect you have a firewall in the way. Try running ntpdate interactively. /etc/init.d/ntp stop # or /etc/init.d/ntp-simple stop for sid ntpdate -u -b $some_ntp_server In particular the -b option will force a time step. The system startup scripts call it with -s too which logs to the system log in /var/log/syslog. But without that you should see errors to the screen. Best not to run ntpdate to step the clock while ntpd is running or confusion would result. So stop ntpd first and start it again afterward. After ntpd is running for a few minutes run: ntpq -p ntpq -c associations And look for strange output. Here is my "normal" output. bob@misery:~$ ntpq -c associations ind assID status conf reach auth condition last_event cnt =========================================================== 1 35540 9424 yes yes none candidat reachable 2 2 35541 9424 yes yes none candidat reachable 2 3 35542 9624 yes yes none sys.peer reachable 2 bob@misery:~$ ntpq -c peers remote refid st t when poll reach delay offset jitter ============================================================================== +tesuji.proulx.c ntp.example.com 3 u 334 1024 377 0.276 -0.363 0.156 +despair.proulx. ntp.example.com 3 u 307 1024 377 0.353 -0.714 0.693 *joseki.proulx.c ntp.example.com 3 u 319 1024 377 0.652 -1.079 0.265 Bob
Attachment:
pgpg2K3PZhhK0.pgp
Description: PGP signature