Thank you for taking the time report a bug and make Ubuntu better.
I haven't tried to reproduce the problem, but I have a few
considerations here.
After a quick search to check whether this problem was already
encountered/handled by other distributions, I found an interesting bug
against chrony o
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089576
Title:
Chrony systemd service isn't restarted in case of an error
To manage notifica
** Description changed:
I'm running on Ubuntu server 20.04 on a GCP VM. In some some rare cases in
which the VM memory stressed,
the chrony service is killed by the OOM.
Since chrony is a very important service which keeps the time in sync, it
mustn't crash and must remain highly available
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089576
Title:
Chrony systemd service isn't restarted in case of an error
To manage notifica
