[Bug 1779966] Re: chrony fails to start, nm-dispatcher hook causes high CPU load

Andreas Hasenack andreas at canonical.com
Tue Jul 10 17:44:32 UTC 2018


Do you have any apparmor messages in the dmesg output of that machine
where chrony is failing to start?

After the first reboot, if you issue a sudo systemctl restart chrony,
does it work? Or same problem?

You said it's a desktop, how is the network brought up there? Is it only
available after the user logs in?

You also said at some point it was a VM, is that just for testing and
debugging this problem, and you have a "real" desktop elsewhere, or is
your real use case that VM?

-- 
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/1779966

Title:
  chrony fails to start, nm-dispatcher hook causes high CPU load

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1779966/+subscriptions



More information about the Ubuntu-server-bugs mailing list