chronyd remains offline after desktop startup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chrony (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
chronyd is supposed to be put online whenever network comes online by the script in /etc/ppp/
$ chronyc tracking
Reference ID : 127.127.1.1 ()
Stratum : 10
Ref time (UTC) : Wed Sep 7 06:40:20 2016
System time : 0.000000000 seconds fast of NTP time
Last offset : 0.000000000 seconds
RMS offset : 0.000000000 seconds
Frequency : 2.686 ppm fast
Residual freq : 0.000 ppm
Skew : 0.000 ppm
Root delay : 0.000000 seconds
Root dispersion : 0.000001 seconds
Update interval : 0.0 seconds
Leap status : Not synchronised
/var/log/boot.log has the following message:
Starting /usr/sbin/
chronyd is running and offline.
The report is filed from an Lubuntu 14.04 system, but I see the exact same behavior on Ubuntu 14.04 LTS and Linux Mint 14.3 Cinnamon.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: chrony 1.29-1
ProcVersionSign
Uname: Linux 3.19.0-68-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed Sep 7 09:18:47 2016
InstallationDate: Installed on 2016-01-27 (223 days ago)
InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: chrony
UpgradeStatus: No upgrade log present (probably fresh install)
On a Desktop system since 2.4.1 (>=Zesty) there is a NetworkManager hook that should work better for a Desktop environment.
But it is also dependent on the command socket to be working.
That I currently address in bug 1746444.
Without that the internal calls to "chronyc online" will get back an "501 Not authorised" and that is all that happens.
I'm dupping this on the remaining blocker 1746444.
FYI: I outlined in bug 1701926 how you can resolve the lack of a valid command socket manually.