Your message dated Wed, 11 Mar 2020 20:50:26 +0000
with message-id <[email protected]>
and subject line Bug#947936: fixed in chrony 3.5-6
has caused the Debian Bug report #947936,
regarding chrony: Does (still) not start properly on boot on buster
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.)
--
947936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947936
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 3.4-4
Severity: important
Dear maintainer:
Apparently, installing chrony does not ensure at all that it will work.
Google has moved from ntp in Debian 9 to chrony in Debian 10 for their
default Debian GCE images, and I discovered this on a lot of GCE
instances having a clock several minutes off.
The problem I found is very similar to the one described here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933370
I believe the best summary of the problem was made by Michael Biebl
here:
https://github.com/systemd/systemd/issues/7104#issuecomment-471329392
Quoting Michael:
> As it stands, the current practice of having systemd-timesyncd.service
> enabled by default (in Debian) and alternative implementations like
> chrony or ntpd declare Conflicts=systemd-timesyncd.service in their
> service file does not work reliably.
AFAIK, this has been fixed on the systemd side in version 241-3 by
dropping the "Conflicts" systemd had on chrony or ntpd.
Unfortunately, AFAIK, conflicts are bi-directional, so apparently the
problem will persist in buster as far as chrony still has conflicts
in the systemd unit file.
I've noticed this problem happens randomly (it happens in some
instances, it does not happens in some others), so I don't have a
"recipe" as such to reproduce it.
However, I have a particular instance at GCE showing this behaviour
which I could try to clone to give you ssh access if required (please
contact me privately for details).
The behaviour is the following:
Both systemd-timesyncd and chrony are enabled (which is the default
on GCE instances). Just after a reboot, "systemctl status chrony" shows this:
● chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset:
enabled)
Active: inactive (dead)
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
and I see this in the boot log:
systemd[1]: Condition check resulted in Network Time Synchronization being
skipped.
If I do "systemctl disable systemd-timesyncd" and reboot, chrony is
properly loaded and it runs.
If I do "systemctl enable systemd-timesyncd" again and reboot, chrony
is shown as "inactive (dead)" again.
At this point, if I edit
/etc/systemd/system/multi-user.target.wants/chrony.service
to remove the Conflicts line and reboot, chrony is properly loaded and it runs.
[ I'm reporting this as "important" because I believe it to be the kind
of bug that should be fixed in a point release of Debian 10 ].
[ Cc to Michael Biebl in case he would like to comment on the issue ].
Thanks.
--- End Message ---
--- Begin Message ---
Source: chrony
Source-Version: 3.5-6
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: SHA256
Format: 1.8
Date: Tue, 10 Mar 2020 19:17:16 +0100
Source: chrony
Architecture: source
Version: 3.5-6
Distribution: unstable
Urgency: medium
Maintainer: Vincent Blut <[email protected]>
Changed-By: Vincent Blut <[email protected]>
Closes: 947936
Changes:
chrony (3.5-6) unstable; urgency=medium
.
* debian/chrony.service:
- Don’t conflict with systemd-timesyncd.service.
A few users complain that chronyd does not start at boot. The way the
Conflict= directive works internally might cause both systemd-timesyncd
and chronyd to be inactive at boot. So by relying solely on the
disable-with-time-daemon.conf drop-in file provided by systemd, we should
get rid of this malfunction while still preventing these two time daemons
from being active at the same time. Kudos notably go to Santiago Vila for
the report and providing SSH access to a GCE instance where the issue was
reproducible and Michael Biebl for debugging. (Closes: #947936)
.
* debian/control:
- Bump Standards-Version to 4.5.0 (no changes required).
- No need to explicitly conflict with ntp as it now provides time-daemon.
.
* debian/copyright:
- Update copyright year for debian/*.
.
* debian/patches/:
- Add allow-clock_adjtime-in-seccomp-filter.patch.
glibc 2.31 switched the adjtimex() function to the clock_adjtime
system call.
.
* debian/tests/upstream-simulation-test-suite:
- Update clknetsim version. This new version supports glibc >= 2.31
headers.
(LP: #1866753)
.
* debian/tests/control:
- Run the upstream-simulation-test-suite as root.
Checksums-Sha1:
79cf01776e6c9c18015c95d5e9cc22eb1e2623de 2330 chrony_3.5-6.dsc
952ad66816def2a30c4e17a07308292573653efd 35820 chrony_3.5-6.debian.tar.xz
Checksums-Sha256:
4a4dcb89fff8e609731af927b178bbec6e798eee30e41d25fc0ea65c0c8390fe 2330
chrony_3.5-6.dsc
fbf12ea6c5866d62fc9d9af331752bc0c2b161f089ecca75e0640239d505f6ef 35820
chrony_3.5-6.debian.tar.xz
Files:
810b6b9b2ee3c11e94adea43138398cd 2330 net optional chrony_3.5-6.dsc
b4511774726331bade917daabd24637b 35820 net optional chrony_3.5-6.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl5pStoACgkQnFyZ6wW9
dQodRgf+Lj0GRRc9f4vkuh6dYggWcQZ7LqWTN632tXDbjhbGYopriG1UzKBr1LFY
sWe8u/gxLD/8n4moh9iYC66dKRPqLJ6XV4yUg4pSKUEiOKtgF6MlkC7boWKlhDat
uzo9znn+El4GB+qfIiWuNTLp8twZQuobbVrQTtAz5GQV1GFIQ1KfuVJhDdUSz2hI
6SL9SO9FV7ECMdHylKbA3j1Wqrdn8mNgwni1TaYFWTUCwOTPAZFWFE3KKea1UMuP
AmJwhwMEOScgQrO2e6ue1qetJP9W9hRFCPlzV9B/p3pbaaXqyWNxhsN2Bvs1FwoY
WZdrqn3sJ4ZdsgsjPyaubkc8eXxO+A==
=lfiR
-----END PGP SIGNATURE-----
--- End Message ---
