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: daemon doesn't automatically 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.0-4+deb9u1
I'm running debian stable (stretch). When I do a fresh
install of chrony, for some reason it doesn't start on boot. This is without
touching any of the config files.
dilinger@e7450:~$ systemctl is-enabled chrony
enabled
dilinger@e7450:~$ systemctl status chrony
● chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: e
Active: inactive (dead)
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
dilinger@e7450:~$ systemctl start chrony
dilinger@e7450:~$ systemctl status chrony
● chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: e
Active: active (running) since Fri 2017-12-01 00:26:01 PST; 1s ago
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
Process: 1489 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)
Main PID: 1491 (chronyd)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/chrony.service
└─1491 /usr/sbin/chronyd
When started manually, here's what's in daemon.log:
Dec 1 00:26:01 e7450 systemd[1]: Starting chrony, an NTP client/server...
Dec 1 00:26:01 e7450 chronyd[1491]: chronyd version 3.0 starting (+CMDMON +NTP
+REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS +IPV6 -DEBUG)
Dec 1 00:26:01 e7450 chronyd[1491]: Frequency 0.000 +/- 1000000.000 ppm read
from /var/lib/chrony/chrony.drift
Dec 1 00:26:01 e7450 systemd[1]: Started chrony, an NTP client/server.
Dec 1 00:26:08 e7450 chronyd[1491]: Selected source 50.116.52.97
I don't see anything in the logs during boot about chrony attempting to
start.
--- 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 ---
