Your message dated Sat, 04 Jul 2026 14:42:58 +0000
with message-id <[email protected]>
and subject line Bug#1011533: fixed in chrony 4.6.1-3+deb13u2
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.6.1-3+deb13u2
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: Wed, 24 Jun 2026 20:05:59 +0200
Source: chrony
Architecture: source
Version: 4.6.1-3+deb13u2
Distribution: trixie
Urgency: medium
Maintainer: Vincent Blut <[email protected]>
Changed-By: Vincent Blut <[email protected]>
Closes: 1011533
Changes:
chrony (4.6.1-3+deb13u2) trixie; 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:
dc3dd7aeb3742667513c0bb70b414df1e41898a5 2898 chrony_4.6.1-3+deb13u2.dsc
37b81456263fb4eba16926116a8387a72103bfb4 44356
chrony_4.6.1-3+deb13u2.debian.tar.xz
871f53b90ef52875fb8d7586c3f7e1d16b09d669 1382552
chrony_4.6.1-3+deb13u2.git.tar.xz
3d9e63e4ef1c9bc84d974dd2a0984f59c255fd94 17532
chrony_4.6.1-3+deb13u2_source.buildinfo
Checksums-Sha256:
0336767d54cc761119ba2ada1a5c5e953b4286444aefaf6e6eea13d01a9ae78f 2898
chrony_4.6.1-3+deb13u2.dsc
a906229f205efdd69032485d8527843f0bd3018351b3f58b133dee56d0c47af9 44356
chrony_4.6.1-3+deb13u2.debian.tar.xz
55309dff267e0c278acd98386d102b3bc2c9bd87af325fe90ed7154f078acc15 1382552
chrony_4.6.1-3+deb13u2.git.tar.xz
4a4a7f063b582f9104e850ca47065492eb3b2c0a4bc5074a3ca833f0c4756087 17532
chrony_4.6.1-3+deb13u2_source.buildinfo
Files:
b759d41fd84da64f10ef05bc513b9fc9 2898 net optional chrony_4.6.1-3+deb13u2.dsc
5e3ddfd53d1f617ec703be8f5f9c2bde 44356 net optional
chrony_4.6.1-3+deb13u2.debian.tar.xz
91c992ee152a1c8d39ee6b4d54ded5f6 1382552 net optional
chrony_4.6.1-3+deb13u2.git.tar.xz
9bae88555fb0a7bba7a23660686cc379 17532 net optional
chrony_4.6.1-3+deb13u2_source.buildinfo
Git-Tag-Info: tag=0d32b72cd99ecfc5f9584806f99e3c70e2a45891
fp=1b939355ac4c35cadfbd739c06a328e00c6ace15
Git-Tag-Tagger: Paul Gevers <[email protected]>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmpIsnEACgkQYG0ITkaD
wHmiNg//f+oTur8hHy0lcjXisgazY813RNqTl6wUcCvQRdEl/nqWebZhQMRYfM5P
Xg3aD/QDq8grh8RL/In84A+DPpRbYyP+Ge8gpdQdcZUybZXqYgoUVlUoo7KGu1zF
am1pI1wi6Hy49WwRWCfUdLl9yLg8HBVZEuSiij8ZYywb8ltddqTYGcSK5141Hpnz
RCWttv8aAl15UrBPMH5ulbsjzsWCjNOKGWtWMxHgOccBCx2Z+qYga4Krvy7IkxeI
tMK/STcvS/osTdMHIdUJjywuJFjrxUqLnoXurfs73lIzS5lkQaJP4ibT92NOADtf
D/6b2ivLDC3kbzSURSmEggNl0S0FiIx7m8dcV+P14tfySN3neipEwrCLSZS6bChs
mfZv9tkUJdahhGcdmhlHsA1aJXEDlM7XWS5/zCIR4vpiQI/aOBefeUqUGHp8xHhH
hUbxApj30GyXyR5zw/EOkKDzgXzWuPAOHcjway/iVWzTXit0ueED8fF4cDpn5t1l
q+iiGqNM/+q2mOxk5M1/VzP4fB03OebTHui/Une1f1+Rc870p9lE5Zoy2GTNybvb
SwLYRtv/SNN2+gwTc1jkRkzM8ZpRsc7bqp6sCLV/MFJ6xT2FgRhsCPA7Gw4DZ5lf
4QyBrUEUgkVtW/Nmm8Ca6+OCwaoSUEu+ThwLRKT7R0xl0X/gtYI=
=+MhZ
-----END PGP SIGNATURE-----
pgppA1oF8iBWz.pgp
Description: PGP signature
--- End Message ---
