Bug#968105: chrony still not started by systemd (on Buster)

Harald Dunkel harri at afaics.de
Sat Aug 8 18:41:12 BST 2020

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)

systemd-timesyncd is not started, either:

root at 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
    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

More information about the Pkg-systemd-maintainers mailing list