chronyd remains offline after desktop startup

Bug #1620936 reported by Niklas Holm
10
This bug affects 2 people
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/ip-up.d/chrony, yet this never happens. After booting to the desktop environment and waiting several minutes with internet connection active, chronyd remains offline as shown by the following command.

$ 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...
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
ProcVersionSignature: Ubuntu 3.19.0-68.76~14.04.1-generic 3.19.8-ckt22
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)

Revision history for this message
Niklas Holm (niklas-holm) wrote :
summary: - cronyd remains offline after desktop startup
+ chronyd remains offline after desktop startup
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chrony (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.