Your message dated Wed, 12 Aug 2020 20:56:54 +0200
with message-id <[email protected]>
and subject line Re: Bug#968105: chrony still not started by systemd (on Buster)
has caused the Debian Bug report #968105,
regarding chrony still not started by systemd (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.)
--
968105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968105
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 241-7~deb10u4
Chrony (3.4-4) is not started at boot time.
# systemctl status chrony
* 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)
systemd-timesyncd is not started, either:
root@nas1:/var/log/chrony# systemctl status systemd-timesyncd
* systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/systemd-timesyncd.service.d
`-disable-with-time-daemon.conf
Active: inactive (dead)
Condition: start condition failed at Sat 2020-08-08 19:06:25 CEST; 9min ago
`- ConditionFileIsExecutable=!/usr/sbin/chronyd was not met
Docs: man:systemd-timesyncd.service(8)
Aug 08 19:06:25 nas1.afaics.de systemd[1]: Condition check resulted in Network
Time Synchronization being skipped.
Of course I found #947936, but this doesn't help. Apparently this
"start condition" thingy is not working correctly. Would you mind
to fix for Buster?
The system is a openmediavault filer. Its supposed to run out of the
box. Not having a proper time synchronisation (even though its
configured correctly in the web GUI) is a serious problem.
Thanx very much. Keep on your good work
Harri
--- End Message ---
--- Begin Message ---
Am 08.08.20 um 19:41 schrieb Harald Dunkel:
> Package: systemd
> Version: 241-7~deb10u4
>
> Chrony (3.4-4) is not started at boot time.
>
> # systemctl status chrony
> * 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)
>
>
> systemd-timesyncd is not started, either:
>
> root@nas1:/var/log/chrony# systemctl status systemd-timesyncd
> * systemd-timesyncd.service - Network Time Synchronization
> Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service;
> enabled; vendor preset: enabled)
> Drop-In: /usr/lib/systemd/system/systemd-timesyncd.service.d
> `-disable-with-time-daemon.conf
> Active: inactive (dead)
> Condition: start condition failed at Sat 2020-08-08 19:06:25 CEST; 9min ago
> `- ConditionFileIsExecutable=!/usr/sbin/chronyd was not met
> Docs: man:systemd-timesyncd.service(8)
>
> Aug 08 19:06:25 nas1.afaics.de systemd[1]: Condition check resulted in
> Network Time Synchronization being skipped.
>
>
> Of course I found #947936, but this doesn't help. Apparently this
> "start condition" thingy is not working correctly. Would you mind
> to fix for Buster?
>
> The system is a openmediavault filer. Its supposed to run out of the
> box. Not having a proper time synchronisation (even though its
> configured correctly in the web GUI) is a serious problem.
The changes that were done in bullseye (i.e. split out
systemd-timesyncd) are not applicable for a stable upload and would not
be acked by the stable release managers.
A couple of remarks:
a/ A default installation should *just work* where systemd-timesyncd is
the only installed and active NTP client
b/ If you customize your installation and decide to use chrony instead,
it's best if you also run "systemctl disable systemd-timesyncd". This
ensures that chrony will start. As you noticed, Conflicts= is
unfortunately not quite suitable to solve this.
Anyway, since this is not going to change for buster I'm going to close
this bug report.
Thanks for understanding.
Michael
signature.asc
Description: OpenPGP digital signature
--- End Message ---
