The information I provided is taken from a VM upon logging in after
initial boot. I provided my chrony.conf as attachment precisely to head
off the question about custom config.
The logs were not clear on why chrony is not starting cleanly.
Regardless, attempts to call chronyc by the NM dispatcher are hanging an
entire CPU. Neither of these are particularly good.
Interestingly, this configuration was working fine for awhile and only
recently started displaying these issues.
** Changed in: chrony (Ubuntu)
Status: Incomplete => New
--
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
