systemd-timesyncd.service not starting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Kubuntu -19.10 (though I believe the problem also exists on prior versions)
Time synchronization not working:
----------
<email address hidden> /lib/systemd/
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no
<email address hidden> /lib/systemd/
● systemd-
Loaded: loaded (/lib/systemd/
Drop-In: /lib/systemd/
Active: inactive (dead) since Sat 2019-11-30 08:21:28 PST; 2min 0s ago
Condition: start condition failed at Sat 2019-11-30 08:23:15 PST; 12s ago
└─ ConditionFileIs
Docs: man:systemd-
Main PID: 813 (code=exited, status=0/SUCCESS)
Status: "Shutting down..."
Nov 30 07:29:50 Crynfyd systemd[1]: Starting Network Time Synchronization...
Nov 30 07:29:51 Crynfyd systemd[1]: Started Network Time Synchronization.
Nov 30 07:30:21 Crynfyd systemd-
Nov 30 08:21:28 Crynfyd systemd[1]: Stopping Network Time Synchronization...
Nov 30 08:21:28 Crynfyd systemd[1]: systemd-
Nov 30 08:21:28 Crynfyd systemd[1]: Stopped Network Time Synchronization.
Nov 30 08:23:15 Crynfyd systemd[1]: Condition check resulted in Network Time Synchronization being ski
----------
The problem has to do with the file
/lib/systemd/
----------
<email address hidden> /lib/systemd/
[Unit]
# don't run timesyncd if we have another NTP daemon installed
ConditionFileIs
ConditionFileIs
ConditionFileIs
ConditionFileIs
----------
I do have virtualbox installed, but not running, so VBoxService is not running.
This means that although the binary is there, it is not providing time sync services, so the system is not time syncing. If I remove the line "ConditionFileI
----------
<email address hidden> /lib/systemd/
<email address hidden> /lib/systemd/
<email address hidden> /lib/systemd/
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
----------
So instead of testing just for the existence of the binary, which is resulting in no time sync service, what it probably should do is check for a running process, and allow the service to start if no other time syncing service is running.
This isn't exactly the same issue as bug 1849156 (that is about ntp condition check conflict, this is virtualbox), but it's close enough as the cause is the same - the drop-in file simply checking for the presence of specific executable files, instead of checking for running process/service.
I'm duping to that bug, but if you disagree please feel free to un-dup.