chrony will still start even if the network isn't up. It will just not report any reachability to peers (or possibly any peers at all). For some reason chrony was straight up not running. Not sure why that was the case.
My guess is the high CPU from the chronyc command invoked by the nm- dispatcher script was because systemd had reserved the control socket. The client ended up spinning talking to a socket going nowhere. The system was also in a weird state where the lightdm login was not appearing until after a login on one of the virtual consoles, so it probably had other issues. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
