On Friday 16 December 2005 2:39 am, Per Jessen wrote:
suillus:~ # ntptrace /usr/sbin/ntpq: read: Connection refused
Is your xntpd actually running? It doesn't look like it.
That may be the problem, since ps -A | grep ntp doesn't reveal it. Here are the last several entries in the ntp log: 30 Oct 10:22:30 ntpd[5269]: synchronized to 67.128.71.75, stratum 2 30 Oct 10:22:30 ntpd[5269]: kernel time sync disabled 0041 30 Oct 10:22:34 ntpd[5269]: synchronized to 209.51.161.238, stratum 1 30 Oct 10:22:34 ntpd[5269]: kernel time sync enabled 0001 30 Oct 10:23:34 ntpd[5269]: synchronized to 67.128.71.75, stratum 2 30 Oct 10:31:07 ntpd[5269]: synchronized to 209.51.161.238, stratum 1 30 Oct 11:40:26 ntpd[5269]: ntpd exiting on signal 15 14 Dec 21:10:50 ntpd[14778]: synchronized to 67.128.71.75, stratum 2 14 Dec 21:10:50 ntpd[14778]: kernel time sync disabled 0041 14 Dec 21:13:01 ntpd[14778]: synchronized to 209.51.161.238, stratum 1 14 Dec 21:16:16 ntpd[14778]: kernel time sync enabled 0001 14 Dec 21:35:49 ntpd[14778]: ntpd exiting on signal 15 14 Dec 21:39:04 ntpd[16264]: synchronized to 67.128.71.75, stratum 2 14 Dec 21:39:08 ntpd[16264]: synchronized to 209.51.161.238, stratum 1 14 Dec 21:43:26 ntpd[16264]: kernel time sync disabled 0041 14 Dec 21:52:06 ntpd[16264]: kernel time sync enabled 0001 14 Dec 23:37:37 ntpd[16264]: ntpd exiting on signal 15 15 Dec 22:53:08 ntpd[13217]: synchronized to 67.128.71.75, stratum 2 15 Dec 22:53:08 ntpd[13217]: kernel time sync disabled 0041 15 Dec 22:56:25 ntpd[13217]: synchronized to 209.51.161.238, stratum 1 15 Dec 22:56:26 ntpd[13217]: kernel time sync enabled 0001 15 Dec 23:32:05 ntpd[13217]: ntpd exiting on signal 15 What seems to be happening is that something is killing ntpd. Some of the entries are probably accounted for by my occasionally doing (as root) /etc/init.d/ntp restart or by actual restarts. There's also the mysterious gap between 30 Oct and 14 Dec. I also have: pwa@suillus:~> ls -l /var/lib/ntp/drift/ntp.drift -rw-r--r-- 1 ntp root 8 2005-12-14 23:35 /var/lib/ntp/drift/ntp.drift And here are the relevant (I think) values from Yast: NTPD_INITIAL_UPDATE AUTO NTPD_OPTIONS -u ntp NTPD_RUN_CHROOTED yes NTPD_CHROOT_FILES (empty) (These all seem to be the defaults.) There's probably a connection between the fact that ntp.drift isn't getting modified and that ntpd isn't running. Any ideas? Thanks. Paul