Your message dated Mon, 2 Dec 2019 17:35:38 +0100
with message-id <[email protected]>
and subject line Re: Bug#883241: chrony: daemon doesn't automatically start
has caused the Debian Bug report #883241,
regarding chrony won't start
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.)
--
883241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883241
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 3.4-4
Severity: normal
Dear Maintainer,
There's a good chance this is the same problem as bug 826695, but
since I don't know that, and this is on buster, I'm making this a
separate report.
May warrant higher severity since it means the program doesn't run by
default. The fact that it is not running is not obvious if you don't
check; I only noticed when my system clock became significantly off of
true time.
Root and other partitions are encrypted logical volumes.
* What led up to the situation?
On buster, restart the system.
* What exactly did you do (or not do) that was effective (or
ineffective)?
systemctl start chrony
* What was the outcome of this action [manual start]?
chrony started and the time is corrected
* What outcome did you expect instead [on restart]?
Startup would be automatic.
I started the kernel with options
debug systemd.log_level=debug systemd.log_target=kmsg loc_buf_len=1M
printk.devkmsg=on
as advised https://freedesktop.org/wiki/Software/systemd/Debugging/
Oddly, this produced less output than usual: journalctl -u chrony
showed nothing. However, everything I usually see from journalctl -u
chrony does appear in the overall logs, below.
It looks as if systemd-timesyncd is creating a stop job for chrony
even though the former includes
#
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
[Unit]
# don't run timesyncd if we have another NTP daemon installed
ConditionFileIsExecutable=!/usr/sbin/ntpd
ConditionFileIsExecutable=!/usr/sbin/openntpd
ConditionFileIsExecutable=!/usr/sbin/chronyd
ConditionFileIsExecutable=!/usr/sbin/VBoxService
which seems to be effective in preventing it from running.
There doesn't seem to be anything in the setup files for
systemd-timesyncd that would cause chrony to stop (no Conflicts
entry); maybe the problem is
Conflicts=systemd-timesyncd.service openntpd.service ntp.service ntpsec.service
in chrony itself.
~# journalctl -b | grep chrony
Jul 29 11:30:43 barley systemd[1]: Pulling in chrony.service/stop from
systemd-timesyncd.service/start
Jul 29 11:30:43 barley systemd[1]: Added job chrony.service/stop to transaction.
Jul 29 11:30:43 barley systemd[1]: Pulling in chrony.service/start from
multi-user.target/start
Jul 29 11:30:43 barley systemd[1]: Added job chrony.service/start to
transaction.
Jul 29 11:30:43 barley systemd[1]: Pulling in sysinit.target/start from
chrony.service/start
Jul 29 11:30:43 barley systemd[1]: Pulling in system.slice/start from
chrony.service/start
Jul 29 11:30:43 barley systemd[1]: Pulling in -.mount/start from
chrony.service/start
Jul 29 11:30:43 barley systemd[1]: Pulling in var.mount/start from
chrony.service/start
Jul 29 11:30:43 barley systemd[1]: Pulling in ntp.service/stop from
chrony.service/start
Jul 29 11:30:43 barley systemd[1]: Pulling in openntpd.service/stop from
chrony.service/start
Jul 29 11:30:43 barley systemd[1]: Pulling in ntpsec.service/stop from
chrony.service/start
Jul 29 11:30:43 barley systemd[1]: Pulling in shutdown.target/stop from
chrony.service/start
Jul 29 11:30:43 barley systemd[1]: Pulling in systemd-timesyncd.service/stop
from chrony.service/start
Jul 29 11:30:43 barley systemd[1]: chrony.service: Looking at job
chrony.service/start conflicted_by=no
Jul 29 11:30:43 barley systemd[1]: chrony.service: Looking at job
chrony.service/stop conflicted_by=no
Jul 29 11:30:43 barley systemd[1]: chrony.service: Fixing conflicting jobs
chrony.service/start,chrony.service/stop by deleting job chrony.service/stop
Jul 29 11:30:43 barley systemd[1]: chrony.service: Installed new job
chrony.service/start as 163
Jul 29 11:30:46 barley systemd[1]: Pulling in chrony.service/stop from
systemd-timesyncd.service/start
Jul 29 11:30:46 barley systemd[1]: Added job chrony.service/stop to transaction.
Jul 29 11:30:46 barley systemd[1]: chrony.service: chrony.service/stop would
change existing job.
Jul 29 11:30:46 barley systemd[1]: chrony.service: Deleting chrony.service/stop
to minimize impact.
Jul 29 11:30:47 barley systemd[1]: Pulling in chrony.service/stop from
systemd-timesyncd.service/start
Jul 29 11:30:47 barley systemd[1]: Added job chrony.service/stop to transaction.
Jul 29 11:30:47 barley systemd[1]: chrony.service: chrony.service/stop would
change existing job.
Jul 29 11:30:47 barley systemd[1]: chrony.service: Deleting chrony.service/stop
to minimize impact.
Jul 29 11:30:47 barley systemd[1]: Pulling in chrony.service/stop from
systemd-timesyncd.service/start
Jul 29 11:30:47 barley systemd[1]: Added job chrony.service/stop to transaction.
Jul 29 11:30:47 barley systemd[1]: chrony.service: chrony.service/stop would
change existing job.
Jul 29 11:30:47 barley systemd[1]: chrony.service: Deleting chrony.service/stop
to minimize impact.
Jul 29 11:30:47 barley systemd[1]: Pulling in chrony.service/stop from
systemd-timesyncd.service/start
Jul 29 11:30:47 barley systemd[1]: Added job chrony.service/stop to transaction.
Jul 29 11:30:47 barley systemd[1]: chrony.service: chrony.service/stop would
change existing job.
Jul 29 11:30:47 barley systemd[1]: chrony.service: Deleting chrony.service/stop
to minimize impact.
Jul 29 11:30:50 barley systemd[1]: Pulling in chrony.service/stop from
systemd-timesyncd.service/start
Jul 29 11:30:50 barley systemd[1]: Added job chrony.service/stop to transaction.
Jul 29 11:30:50 barley systemd[1]: Keeping job chrony.service/stop because of
systemd-timesyncd.service/start
Jul 29 11:30:50 barley systemd[1]: chrony.service: Job 163 chrony.service/start
finished, result=canceled
Jul 29 11:30:50 barley systemd[1]: chrony.service: Installed new job
chrony.service/stop as 831
Jul 29 11:30:50 barley systemd[1]: chrony.service: Job 831 chrony.service/stop
finished, result=done
Jul 29 11:30:52 barley systemd[1]: systemd-timesyncd.service:
ConditionFileIsExecutable=!/usr/sbin/chronyd failed.
Jul 29 11:30:53 barley kernel: audit: type=1400 audit(1564425053.035:8):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/sbin/chronyd" pid=1294 comm="apparmor_parser"
Jul 29 11:30:53 barley audit[1294]: AVC apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/sbin/chronyd" pid=1294
comm="apparmor_parser"
Jul 29 11:30:53 barley systemd[1]: Pulling in chrony.service/stop from
systemd-timesyncd.service/start
Jul 29 11:30:53 barley systemd[1]: Added job chrony.service/stop to transaction.
Jul 29 11:30:54 barley systemd[1]: Found redundant job chrony.service/stop,
dropping from transaction.
Jul 29 11:30:57 barley systemd[1]: Pulling in chrony.service/stop from
systemd-timesyncd.service/start
Jul 29 11:30:57 barley systemd[1]: Added job chrony.service/stop to transaction.
Jul 29 11:30:58 barley systemd[1]: Found redundant job chrony.service/stop,
dropping from transaction.
Jul 29 11:30:58 barley systemd[1]: Pulling in chrony.service/stop from
systemd-timesyncd.service/start
Jul 29 11:31:00 barley systemd[1]: Pulling in chrony.service/stop from
systemd-timesyncd.service/start
Jul 29 11:31:00 barley systemd[1]: Added job chrony.service/stop to transaction.
Jul 29 11:31:12 barley systemd[1]: Found redundant job chrony.service/stop,
dropping from transaction.
Jul 29 11:31:28 barley systemd[1]: Pulling in chrony.service/stop from
systemd-timesyncd.service/start
Jul 29 11:31:49 barley systemd[1]: Added job chrony.service/stop to transaction.
Jul 29 11:32:11 barley systemd[1]: Pulling in chrony.service/stop from
systemd-timesyncd.service/start
I can provide the whole journal if you want.
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
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.118
ii init-system-helpers 1.56+nmu1
ii iproute2 4.20.0-2
ii libc6 2.28-10
ii libcap2 1:2.25-2
ii libedit2 3.1-20181209-1
ii libnettle6 3.4.1-1
ii libseccomp2 2.3.3-4
ii lsb-base 10.2019051400
ii ucf 3.0038+nmu1
chrony recommends no packages.
Versions of packages chrony suggests:
ii dnsutils 1:9.11.5.P4+dfsg-5.1
ii networkd-dispatcher 2.0-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 241-3
On Sat, 5 Oct 2019 02:43:22 +0200 Michael Biebl <[email protected]> wrote:
> Seems like Conflicts= do not work reliably to ensure the
> systemd-timesyncd.service is not started during boot.
>
> See also the upstream bug report
> https://github.com/systemd/systemd/issues/7104
>
> We've re-added the Conditions to systemd-timesyncd.service.
> #
> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
> [Unit]
> # don't run timesyncd if we have another NTP daemon installed
> ConditionFileIsExecutable=!/usr/sbin/ntpd
> ConditionFileIsExecutable=!/usr/sbin/openntpd
> ConditionFileIsExecutable=!/usr/sbin/chronyd
> ConditionFileIsExecutable=!/usr/sbin/VBoxService
>
>
> This should ensure systemd-timesyncd.service is not started if chrony is
> installed.
>
> Andres, can you still reproduce the problem?
We re-added disable-with-time-daemon.conf in 241-3 and with that drop-in
I successfully tested that chrony, ntp and openntpd are started during
boot (even if systemd-timesyncd is enabled).
I thus consider this issue fixed and will close this bug report for
version 241-3.
If someone still can reproduce the issue with a version >= 241-3, please
let us know and we will reopen the bug report.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
