After a reboot where chrony isn't running, can you run these commands and show their outputs:
sudo systemd-analyze critical-path sudo journalctl -o short-monotonic -u systemd-timesyncd.service -u chrony.service I'll do the same in my vm where chrony is working and let's compare notes. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to chrony in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs