Thank you for taking the time to file a bug report. There is not enough information to begin working on this or narrowing down where the issue may be. Are you running a custom configuration for chrony? What other changes were made to the system? Any other data you can pass on to help triage the issue?
Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: chrony (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs