It does seem to happen on every boot and it seems timesyncd is the
problem:
$ systemctl is-enabled systemd-timesyncd
enabled
This did the trick then:
service {"systemd-timesyncd":
ensure => stopped,
enable => false,
hasstatus => true,
}
Seems more natural for the opposite to be the default. If
chrony/ntp/openntpd is installed then the systemd version is disabled.
It's strange that a simple "apt install chrony" doesn't result in a
running chrony replacing systemd-timesyncd. The user has specifically
decided to install chrony so it seems natural to assume he wants that
instead of systemd and doesn't need to figure out why it's not running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779621
Title:
chrony exits unexpectedly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1779621/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
