reassign 947936 chrony,systemd thanks I am unsure at this point where is exactly the problem.
I have several test instances at GCE (running buster) where chrony does not start even if it's enabled. By trial and error I managed to make chrony to start again properly if I do this: journalctl --rotate init 6 So the natural question would be: What kind of bug in systemd can make it not to start a service at all when there is a "bad" journal? Thanks.
