Comment 8 for bug 1779621

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?