Your message dated Sat, 04 Jul 2026 10:32:24 +0000
with message-id <[email protected]>
and subject line Bug#1011533: fixed in chrony 4.3-2+deb12u3
has caused the Debian Bug report #1011533,
regarding chrony: if-up.d snippet occasionally fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1011533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011533
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 4.6.1-3+deb13u1
Severity: normal
X-Debbugs-Cc: [email protected]
I’ve found out that sometimes, networking.service is failed after boot
because the if-up.d snippet runs “chronyc onoffline”, returning
“501 Not authorised” and a nōn-zero exit status.
This is because its service file has no dependency either way on
the network being up (apparently, chrony can be started before that
relying on chronyc to register ifstate changes?) so chrony is sometimes
started in the same second as that command runs and then is in a state
where it accepts the chronyc command but refuses it, instead of e.g.
keeping it in a queue until ready to serve it.
I’ve solved this locally by changing the if-up.d script to retry with
backoff, but would welcome an official fix or workaround.
│ #!/bin/bash
│
│ test -x /usr/sbin/chronyd || exit 0
│ test -e /run/chrony/chronyd.pid || exit 0
│
│ chronyc onoffline 2>&1 | logger -it chronyc-onoffline
│ rv=${PIPESTATUS[0]}
│ logger -it chronyc-onoffline "=== ${rv:-'???'}"
│ i=0
│ for try_interval in 1 3 12; do
│ if test "$rv" -gt 0; then
│ sleep $try_interval
│ chronyc onoffline 2>&1 | logger -it
chronyc-onoffline-retry
│ rv=${PIPESTATUS[0]}
│ logger -it chronyc-onoffline-retry$((++i)) "===
${rv:-'???'}"
│ fi
│ done
│ exit $rv
-- System Information:
Debian Release: 13.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.90+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to C.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chrony depends on:
ii adduser 3.152
ii init-system-helpers 1.69~deb13u1
ii iproute2 6.15.0-1
ii libc6 2.41-12+deb13u3
ii libcap2 1:2.75-10+deb13u1+b1
ii libedit2 3.1-20250104-1
ii libgnutls30t64 3.8.9-3+deb13u4
ii libnettle8t64 3.10.1-1
ii libseccomp2 2.6.0-2
ii tzdata 2026b-0+deb13u1
ii ucf 3.0052
chrony recommends no packages.
Versions of packages chrony suggests:
ii bind9-dnsutils [dnsutils] 1:9.20.23-1~deb13u1
ii dnsutils 1:9.18.41-1~deb12u1
pn networkd-dispatcher <none>
-- Configuration Files:
/etc/network/if-up.d/chrony changed:
test -x /usr/sbin/chronyd || exit 0
test -e /run/chrony/chronyd.pid || exit 0
chronyc onoffline 2>&1 | logger -it chronyc-onoffline
rv=${PIPESTATUS[0]}
logger -it chronyc-onoffline "=== ${rv:-'???'}"
exit $rv
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chrony
Source-Version: 4.3-2+deb12u3
Done: Vincent Blut <[email protected]>
We believe that the bug you reported is fixed in the latest version of
chrony, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vincent Blut <[email protected]> (supplier of updated chrony package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 02 Jul 2026 15:56:53 +0200
Source: chrony
Architecture: source
Version: 4.3-2+deb12u3
Distribution: bookworm
Urgency: medium
Maintainer: Vincent Blut <[email protected]>
Changed-By: Vincent Blut <[email protected]>
Closes: 1011533
Changes:
chrony (4.3-2+deb12u3) bookworm; urgency=medium
.
* debian/chrony.if-{post-down,up}:
- Adjust the if-up and if-down hook scripts so that they always exit
successfully. (Closes: #1011533)
Checksums-Sha1:
0684242c62f0fc788a7c988b87a62e90a765e871 2873 chrony_4.3-2+deb12u3.dsc
45eca757b74064e473b7c5236cc413074690081e 41876
chrony_4.3-2+deb12u3.debian.tar.xz
3de2025133f117fac14a6684102e0a929a3b69fb 1220684
chrony_4.3-2+deb12u3.git.tar.xz
59fbdf5a1728436fedb9334c3d911748ae1f083a 17524
chrony_4.3-2+deb12u3_source.buildinfo
Checksums-Sha256:
cdc58b9fcb11d9799dd7c5936c1a1666ff00d60e6cfd2b80687b49e589d7e2b5 2873
chrony_4.3-2+deb12u3.dsc
b2249988f534e724e89c9c3f9785d40eb083ee712780f89cbcb1d4b9fba29882 41876
chrony_4.3-2+deb12u3.debian.tar.xz
1749ffa3456d364951998a2ef5095981f1ff6f7789482b647b5a6e76233eff3f 1220684
chrony_4.3-2+deb12u3.git.tar.xz
53bc6cfda296af84c4e64e85a55bffac9ee66eed7492b1629678e2f903c37c3c 17524
chrony_4.3-2+deb12u3_source.buildinfo
Files:
3dab963a37de76d447773170298253cf 2873 net optional chrony_4.3-2+deb12u3.dsc
0cfcb9b183097e50187cb655cf0314b6 41876 net optional
chrony_4.3-2+deb12u3.debian.tar.xz
91570083241de0fecabe8a15cffb4fae 1220684 net optional
chrony_4.3-2+deb12u3.git.tar.xz
4db8346836791b6de2276ebefc0d01e5 17524 net optional
chrony_4.3-2+deb12u3_source.buildinfo
Git-Tag-Info: tag=76c8ae89704bb3c8d62debb4e8ead47c0dcb3111
fp=1b939355ac4c35cadfbd739c06a328e00c6ace15
Git-Tag-Tagger: Paul Gevers <[email protected]>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmpIshQACgkQYG0ITkaD
wHmjpQ//ZF041QrmACcZ1E6LI9nKnWTl7xYCV1LlQd2ZIfl3z3EEA2vet/Qt1LVL
1CzttfPmz5X1tRqDHwEkv8kQLkSfICaQIffCegJp2UCzqITBSDj2b8iLKre9L0L6
NNhvSeWeVT9xL1RPJJMWiskqbySRrUrFupnTZwHLb0YBP+0tGjjESl/L4VYsZd0V
j9G19mJa6cI9ccD//DdYluCzASHno+HETzpDvUpIEo/gKYlttsIVGUwbp0l/+VFO
ssq6jHUaNU4TjtMMZkYd4XQkbnvYmUh3H0Kkfg4ewEIIoLT14AtpzhWK9GHnqn8h
r0JP2xp5MBTSvJyUZxfkwWGar7FU6S9dwEbbxgtsMDXOm6+sJPtdHBoRA65i33wP
NFcAAg4hJt6S1e9vfLtxqhDEaYOKxsxeydtPsnccgp8qatI4effxT9pblF94dZp4
Bfehu4X+abU05tfH0GS4rvjcfBXpoAbgbz2J2OTR+xqJK2PaUekvyrZOMP/ykUd1
yw7mp7Y8gavm1lDsoWbQUP8RZ55+uxzuTHqE0zjBlJ8LB4W3YBEosAwLAWVbPk83
SreqtvMGbgfpr0H2nMiMpPnKWCz/SNjA8Y/I5obOnNGSb5YKKK1UXFg8sfiRguVO
Sxm5ZDYWpGJ4PkVrEvckexcrwDRYsV7I7/6HxgExjYWQh4Tglhg=
=eacS
-----END PGP SIGNATURE-----
pgp70er9JFN35.pgp
Description: PGP signature
--- End Message ---
