[pkg-ntp-maintainers] Bug#461419: ntpd stopped working

Fri Jan 18 11:37:46 UTC 2008

Package: ntp
Version: 1:4.2.4p4+dfsg-3
Severity: important

For an unknown reason, ntpd stopped working (the time is not longer
corrected), probably since about 2008-01-16 18:28:26 +0100 as:

-rw-r--r-- 1 ntp ntp 9 2008-01-16 18:28:26 /var/lib/ntp/ntp.drift

I've restarted it with

  /etc/init.d/ntp restart

but it still doesn't work.

vin:~> ps -fwp `pgrep ntpd`
UID        PID  PPID  C STIME TTY          TIME CMD
ntp      18567     1  0 11:27 ?        00:00:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -u 104:110 -g

Here's what's in the logs concerning ntp:

Jan 16 17:41:30 vin ntpd[11909]: synchronized to 193.48.168.22, stratum 2
Jan 16 17:41:30 vin ntpd[11909]: kernel time sync status change 0001
Jan 16 18:07:13 vin ntpd[11909]: time reset +0.254791 s

and

Jan 18 11:27:57 vin ntpd[11909]: ntpd exiting on signal 15
Jan 18 11:27:59 vin ntpd[18566]: ntpd 4.2.4p4 at 1.1520-o Sun Jan 13 11:21:22 UTC 2008 (1)
Jan 18 11:27:59 vin ntpd[18567]: precision = 1.000 usec
Jan 18 11:27:59 vin ntpd[18567]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Jan 18 11:27:59 vin ntpd[18567]: Listening on interface #1 wildcard, ::#123 Disabled
Jan 18 11:27:59 vin ntpd[18567]: Listening on interface #2 lo, ::1#123 Enabled
Jan 18 11:27:59 vin ntpd[18567]: Listening on interface #3 eth0, fe80::213:72ff:fe28:13ec#123 Enabled
Jan 18 11:27:59 vin ntpd[18567]: Listening on interface #4 lo, 127.0.0.1#123 Enabled
Jan 18 11:27:59 vin ntpd[18567]: Listening on interface #5 eth0, 140.77.13.170#123 Enabled
Jan 18 11:27:59 vin ntpd[18567]: kernel time sync status 0040
Jan 18 11:27:59 vin ntpd[18567]: frequency initialized -255.706 PPM from /var/lib/ntp/ntp.drift

The ntp package was upgraded on 2008-01-14 09:28:26.

I've searched on Google and found:

  https://support.ntp.org/bugs/show_bug.cgi?id=780
  "kernel time sync error 0001"

I don't know if this is related to my problem, but if I understand
correctly, this ntp bug has been closed as invalid because they
claim that this is a bug in the Linux kernel.

I've attached my config file.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.23-1-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages ntp depends on:
ii  adduser                       3.105      add and remove users and groups
ii  libc6                         2.7-6      GNU C Library: Shared libraries
ii  libcap1                       1:1.10-14  support for getting/setting POSIX.
ii  libreadline5                  5.2-3      GNU readline and history libraries
ii  libssl0.9.8                   0.9.8g-4   SSL shared libraries
ii  lsb-base                      3.1-24     Linux Standard Base 3.1 init scrip
ii  netbase                       4.30       Basic TCP/IP networking system

Versions of packages ntp recommends:
ii  perl                          5.8.8-12   Larry Wall's Practical Extraction 

-- no debconf information
-------------- next part --------------
# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help

driftfile /var/lib/ntp/ntp.drift

# Enable this if you want statistics to be logged.
#statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable

# You do need to talk to an NTP server or two (or three).
#server ntp.your-provider.example

# pool.ntp.org maps to about 1000 low-stratum NTP servers.  Your server will
# pick a different set every time it starts up.  Please consider joining the
# pool: <http://www.pool.ntp.org/join.html>
server 0.debian.pool.ntp.org iburst dynamic
server 1.debian.pool.ntp.org iburst dynamic
server 2.debian.pool.ntp.org iburst dynamic
server 3.debian.pool.ntp.org iburst dynamic

# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
# details.  The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
# might also be helpful.
#
# Note that "restrict" applies to both servers and clients, so a configuration
# that might be intended to block requests from certain clients could also end
# up blocking replies from your own upstream servers.

# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery

# Local users may interrogate the ntp server more closely.
restrict 127.0.0.1
restrict ::1

# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust

# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
#broadcast 192.168.123.255

# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines.  Please do this only if you trust everybody on the network!
#disable auth
#broadcastclient