[pkg-ntp-maintainers] Bug#465752: ntp: Default distribution does not form peer relationships

[Moshe Yudkowsky]

Subject: ntp: Default distribution does not form peer relationships
Package: ntp
Version: 1:4.2.4p4+dfsg-3
Severity: important


I have two Debian systems running. With the identical ntp.conf, one (AMD
k7) will sync while the other (AMD64 as shown below) will not. I cannot
even persuade the AMD64 system to peer with the AMD k7 system.

My config file reads:

driftfile /var/lib/ntp/ntp.drift

statsdir /var/log/ntpstats/

logconfig =syncstatus +allevents +allinfo +allstatus
logfile	/var/log/ntpd

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

server nist1.datum.com

server 0.debian.pool.ntp.org dynamic iburst
server 1.debian.pool.ntp.org dynamic iburst
server 2.debian.pool.ntp.org dynamic iburst
server 3.debian.pool.ntp.org dynamic iburst
server 0.us.pool.ntp.org dynamic iburst
server 1.us.pool.ntp.org dynamic iburst
server 2.us.pool.ntp.org dynamic iburst
server 3.us.pool.ntp.org dynamic iburst

server bagpipes.local



I've added this rather long list in order to find *something* to sync
with. At ntp start time, I get in the log:

10 Feb 10:17:37 ntpd[15698]: system event 'event_peer/strat_chg' (0x04)
status 'sync_alarm, sync_ntp, 2 events, event_restart' (0xc621)
10 Feb 10:17:37 ntpd[15698]: synchronized to 216.184.20.83, stratum 3
10 Feb 10:17:38 ntpd[15698]: time reset +1.456355 s
10 Feb 10:17:38 ntpd[15698]: kernel time sync status change 0001

However,

s# ntpq -c as

ind assID status  conf reach auth condition  last_event cnt
===========================================================
  1 31069  8000   yes   yes  none    reject
  2 31070  9024   yes   yes  none    reject   reachable  2
  3 31071  9024   yes   yes  none    reject   reachable  2
  4 31072  9024   yes   yes  none    reject   reachable  2
  5 31073  9024   yes   yes  none    reject   reachable  2
  6 31074  9024   yes   yes  none    reject   reachable  2
  7 31075  9024   yes   yes  none    reject   reachable  2
  8 31076  9024   yes   yes  none    reject   reachable  2
627 ntpstats# date
Sun Feb 10 10:38:55 CST 2008

In other words, after 20 minutes all outside servers and the inside
server are still listed as "rejected." I see multiple "unreach" events
in the log.

# ntpdc -c peers -c sysinfo
     remote           local      st poll reach  delay   offset    disp
=======================================================================
=clock.trit.net  172.28.54.162    2   64  377 0.07658 24.532540 0.07133
=63.240.161.99   172.28.54.162    2   64  377 0.01187 26.785723 0.06363
=mick.eng.uiowa. 172.28.54.162    2   64  377 0.01299 32.043092 0.04242
=hydrogen.cert.u 172.28.54.162    2   64  377 0.08910 36.593320 0.03636
=bagpipes.local  172.28.54.162    2   64  377 0.00017 27.291048 0.06699
=nick125.com     172.28.54.162    3   64  377 0.12784 34.653144 0.04703
=nist1.symmetric 172.28.54.162    1   64    0 0.00000  0.000000 3.99217
=dtype.org       172.28.54.162    2   64  377 0.06665 33.784147 0.05498
system peer:          0.0.0.0
system peer mode:     unspec
leap indicator:       11
stratum:              16
precision:            -20
root distance:        0.00000 s
root dispersion:      0.02193 s
reference ID:         [83.84.69.80]
reference time:       00000000.00000000  Thu, Feb  7 2036  0:28:16.000
system flags:         auth monitor ntp kernel stats
jitter:               0.144241 s
stability:            0.000 ppm
broadcastdelay:       0.003998 s
authdelay:            0.000000 s


I am running both systems behind a firewall. There are no restrict
statements in either config file. The firewall does not have any
particular rules regarding the

Finally, the Enhanced Real Time Clock of this particular kernel seems to
be enabled:
CONFIG_RTC=y

according to /boot/config-2.6.24-1-amd64.

Please let me know if I can provide further information. I've spent a
great deal of time debugging, but I am at a loss to explain why a fresh,
clean install doesn't work "out of the box" in the same network as one
other Debian unstable as well as a Mac and Windows box.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
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