Ubuntu
chrony package

  1. Bug #2004525
  2. Comment #7

Comment 7 for bug 2004525

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

What do we know so far:

1. The issue in Pauls log was:
Feb 2 11:10:26 dns chronyd[356]: Fatal error : Could not open /run/chrony/chronyd.pid : Permission denied
Feb 2 11:10:26 dns chronyd-starter.sh[354]: Could not open /run/chrony/chronyd.pid : Permission denied

2. It was not apparmor as tuning it back just works for him :-/

3. it was not reproducible in clean VMs, nor on other focal->jammy upgrades nor on Pauls system later on.

:-/

We need to find what is odd for those that are affected by this to fix it.
Keeping it "incomplete"