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-
A key difference between a vm and a "real" desktop could be networking,
specially if wifi is involved. For example, in some cases the network
might only be available after the user logs in. Do you think this could
have been the case here?
--
You received this bug notification because you are a
A key difference between a vm and a "real" desktop could be networking,
specially if wifi is involved. For example, in some cases the network
might only be available after the user logs in. Do you think this could
have been the case here?
--
You received this bug notification because you are a
icarus is my virtual desktop to test all manner of things. It is so
named for if I fly it too close to the sun I just rebuild it. As such, I
did just that, and was unable to reproduce this issue.
** Changed in: chrony (Ubuntu)
Status: New => Invalid
--
You received this bug notification
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
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
Noticed another chrony issue, bug 1779621, come in about failing to
start. If you wouldn't mind reading over that and seeing if you have
similar issues that might be good.
I am going to wait for a chrony expert to get back from vacation and
have him review both of these.
--
You received this
ptp_kvm is being loaded in /etc/modules on my machine
--
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
Ah sorry I missed the chrony attachment!
The only differences appear to be:
> refclock PHC /dev/ptp_kvm poll 3 dpoll -2 refid KVM
> server atlantis-int.home.nivex.net offline
Did your system have /dev/ptp_kvm already? My test bionic VM does not
have that device.
$ ethtool -T ens3
...
PTP
Ah! I found a system that has it I'll try to reproduce there on Monday.
On the host:
/dev/ptp0
and
$ ethtool -T eno1
...
PTP Hardware Clock: 0
...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
** Attachment added: "chrony.conf"
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1779966/+attachment/5159357/+files/chrony.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779966
Jul 3 19:44:07 icarus systemd[1]: chrony.service: Start operation timed out.
Terminating.
Jul 3 19:44:07 icarus systemd[1]: chrony.service: Failed with result 'timeout'.
Jul 3 19:44:07 icarus systemd[1]: Failed to start chrony, an NTP client/server.
--
You received this bug notification
14 matches
Mail list logo
