Package: ntpsec
Version: 1.1.9+dfsg1-4
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I don't want to bother the national ntp pool servers more often than necessary.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Here are the server and pool statements from /etc/ntpsec/ntp.conf:
rbthomas@cube:~$ egrep '^(server|pool)' /etc/ntpsec/ntp.conf
server pips.rcthomas.org minpoll 3 maxpoll 8 iburst prefer
pool pool.rcthomas.org minpoll 3 maxpoll 8 prefer iburst
pool us.pool.ntp.org minpoll 6 maxpoll 10 iburst
server 127.127.1.1 iburst
The servers marked "rcthomas.org" are on the local home network.
pips.rcthomas.org is a local gps synchronized ntp server.
Everything else is from the us.pool.ntp.org national pool.
* What was the outcome of this action?
After a delay the poll numbers all migrate up to 256, but seem to stop there.
Here's what I see:
rbthomas@cube:~$ ntpq -p
remote refid st t when poll
reach delay offset jitter
=======================================================================================================
*pips.rcthomas.org .GPS. 1 u 190 256
377 1.3438 -0.9604 0.5393
pool.rcthomas.org .POOL. 16 p - 256
0 0.0000 0.0000 0.0019
us.pool.ntp.org .POOL. 16 p - 256
0 0.0000 0.0000 0.0019
LOCAL(1) .LOCL. 13 l - 64
0 0.0000 0.0000 0.0019
-173.0.48.220.reverse.wowrack.com 192.168.10.254 2 u 517 512
377 15.2537 21.2694 1.0572
+triton.ellipse.net 128.252.19.1 2 u 146 256
177 58.6618 0.7304 5.0250
+ip7.nsg.sbbsnet.net 129.6.15.29 2 u 966 256
10 65.4259 5.3153 1.6917
+half.rcthomas.org 192.168.1.15 2 u 196 256
377 0.4804 -0.8793 0.2603
+sheeva.rcthomas.org 192.168.1.15 2 u 108 256
377 0.5064 0.4234 0.3130
+ultimate.rcthomas.org 192.168.1.15 2 u 158 256
377 0.5294 -0.7818 0.2372
+toshiba.rcthomas.org 192.168.1.15 2 u 129 256
377 0.4931 -1.0025 0.3729
* What outcome did you expect instead?
I expected to see the "us.pool.ntp.org" ".POOL." line showing poll at 1024, and
see at least some of the
servers from that pool with pool values over 256.
However, the only one with a value over 256 is the wowrack.com server with 512.
But that is also the only server flagged with a "-" indicating that it is not
in the running and will be
removed soon.
Is this a bug, or is there some sort of grand design that I'm not taking into
account?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (100, 'unstable')
Architecture: armhf (armv7l)
Kernel: Linux 5.8.0-2-armmp (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ntpsec depends on:
ii adduser 3.118
ii init-system-helpers 1.58
ii libbsd0 0.10.0-1
ii libc6 2.31-3
ii libcap2 1:2.43-1
ii libssl1.1 1.1.1g-1
ii lsb-base 11.1.0
ii netbase 6.1
ii python3 3.8.2-3
ii python3-ntp 1.1.9+dfsg1-4
ii tzdata 2020a-1
Versions of packages ntpsec recommends:
ii cron [cron-daemon] 3.0pl1-136
ii systemd 246.6-1
Versions of packages ntpsec suggests:
ii apparmor 2.13.4-3
pn certbot <none>
ii ntpsec-doc 1.1.9+dfsg1-4
ii ntpsec-ntpviz 1.1.9+dfsg1-4
-- Configuration Files:
/etc/default/ntpsec changed:
NTPD_OPTS="-g -N"
IGNORE_DHCP="yes"
/etc/ntpsec/ntp.conf changed:
driftfile /var/lib/ntpsec/ntp.drift
leapfile /usr/share/zoneinfo/leap-seconds.list
statsdir /var/log/ntpsec/
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
tos maxclock 11
tos minclock 7 minsane 5
server pips.rcthomas.org minpoll 3 maxpoll 8 iburst prefer
pool pool.rcthomas.org minpoll 3 maxpoll 8 prefer iburst
pool us.pool.ntp.org minpoll 6 maxpoll 10 iburst
server 127.127.1.1 iburst
fudge 127.127.1.1 stratum 13 # everybody else
restrict default kod nomodify nopeer noquery limited
restrict 127.0.0.1
restrict ::1
restrict 192.168.0.0 mask 255.255.248.0 nomodify
restrict 2001:4978:02d2:0001::0 mask ffff:ffff:ffff:ffff:0000:0000:0000:0000
nomodify
-- no debconf information
