I did an experiment with a bionic VM, where I installed chronyd and removed the "makestep" line. I then paused the VM and let it be for a while. About an hour later I unpaused it, and the clock was of course off. I rebooted it, and it came back up just fine with chronyd running and the clock adjusted.
It would help if you could give me some steps to try to reproduce this issue. Was your /var/log/chrony directory also empty during these apparent crashes? Could you also please run "sudo systemctl status chronyd" right after the problem happened? -- 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
