comment out line: ConditionFileIsExecutable=!/usr/sbin/VBoxService
works for me.
I had to comment out so line:
ConditionFileIsExecutable=!/usr/sbin/VBoxService
Both are commented out and timesyncd works.
Thank you.
Petr
út 11. 2. 2020 v 7:10 odesílatel Mark - Syminet <email address hidden>
napsal:
> Got bit by this as well, recall fixing it a few years ago but must have
> clobbered my changes on upgrade bionic -> eoan? Having VirtualBox
> installed broke it, fix was to comment out this line in
> /lib/systemdd/system/systemd-timesyncd.service.d and restart systemd:
>
> ConditionFileIsExecutable=!/usr/sbin/VBoxService
>
> Don't recall being asked about a config file change during upgrade
> although maybe it did and didn't remember. Further info here:
>
> https://askubuntu.com/questions/940311/time-in-ubuntu-16-04-not-
> updating-from-internet#1005355
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1849156
>
> Title:
> systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
> installed
>
> Status in ntp package in Ubuntu:
> Confirmed
> Status in systemd package in Ubuntu:
> Confirmed
> Status in ntp source package in Eoan:
> Confirmed
> Status in systemd source package in Eoan:
> Confirmed
> Status in ntp source package in Focal:
> Confirmed
> Status in systemd source package in Focal:
> Confirmed
>
> Bug description:
> Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd-
> timesyncd.service.d/disable-with-time-daemon.conf. This prevents
> systemd-timesyncd.service from starting if the ntp package has been
> installed. However, ntp.service has a Conflicts directive for
> systemd-timesyncd.service. If both services are enabled, neither will
> start on boot. This breaks upgrades from < 19.10 to 19.10 for systems
> that have both ntp and systemd installed.
>
> Possible workarounds:
>
> - Uninstall ntp
> - Disable systemd-timesyncd.service
>
> % lsb_release -rd
> Description: Ubuntu 19.10
> Release: 19.10
>
> % apt-cache policy systemd
> systemd:
> Installed: 242-7ubuntu3
> Candidate: 242-7ubuntu3
> Version table:
> *** 242-7ubuntu3 500
> 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main
> amd64 Packages
> 100 /var/lib/dpkg/status
>
> % apt-cache policy ntp
> ntp:
> Installed: 1:4.2.8p12+dfsg-3ubuntu2
> Candidate: 1:4.2.8p12+dfsg-3ubuntu2
> Version table:
> *** 1:4.2.8p12+dfsg-3ubuntu2 500
> 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu
> eoan/universe amd64 Packages
> 100 /var/lib/dpkg/status
>
> % dpkg -S
> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
> systemd:
> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
>
> % sudo systemctl status ntp
> ● ntp.service - Network Time Service
> Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor
> preset: enabled)
> Active: inactive (dead)
> Docs: man:ntpd(8)
>
> % sudo systemctl status systemd-timesyncd.service
> ● systemd-timesyncd.service - Network Time Synchronization
> Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service;
> enabled; vendor preset: enabled)
> Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
> └─disable-with-time-daemon.conf
> Active: inactive (dead)
> Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
> Docs: man:systemd-timesyncd.service(8)
>
> Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
> Time Synchronization being skipped.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1849156/+subscriptions
>
hi, thank you for reply.
comment out line: ConditionFileIs Executable= !/usr/sbin/ VBoxService
works for me.
I had to comment out so line: Executable= !/usr/sbin/ VBoxService
ConditionFileIs
Both are commented out and timesyncd works.
Thank you.
Petr
út 11. 2. 2020 v 7:10 odesílatel Mark - Syminet <email address hidden>
napsal:
> Got bit by this as well, recall fixing it a few years ago but must have system/ systemd- timesyncd. service. d and restart systemd: Executable= !/usr/sbin/ VBoxService /askubuntu. com/questions/ 940311/ time-in- ubuntu- 16-04-not- from-internet# 1005355 /bugs.launchpad .net/bugs/ 1849156 timesyncd. service broken on upgrade to 19.10 if ntp was system/ systemd- service. d/disable- with-time- daemon. conf. This prevents timesyncd. service from starting if the ntp package has been timesyncd. service. If both services are enabled, neither will timesyncd. service us-east- 1.ec2.archive. ubuntu. com/ubuntu eoan/main dpkg/status dfsg-3ubuntu2 dfsg-3ubuntu2 dfsg-3ubuntu2 500 us-east- 1.ec2.archive. ubuntu. com/ubuntu dpkg/status system/ systemd- timesyncd. service. d/disable- with-time- daemon. conf system/ systemd- timesyncd. service. d/disable- with-time- daemon. conf system/ ntp.service; enabled; vendor timesyncd. service timesyncd. service - Network Time Synchronization system/ systemd- timesyncd. service; system/ systemd- timesyncd. service. d with-time- daemon. conf timesyncd. service( 8) /bugs.launchpad .net/ubuntu/ +source/ ntp/+bug/ 1849156/ +subscriptions
> clobbered my changes on upgrade bionic -> eoan? Having VirtualBox
> installed broke it, fix was to comment out this line in
> /lib/systemdd/
>
> ConditionFileIs
>
> Don't recall being asked about a config file change during upgrade
> although maybe it did and didn't remember. Further info here:
>
> https:/
> updating-
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> systemd-
> installed
>
> Status in ntp package in Ubuntu:
> Confirmed
> Status in systemd package in Ubuntu:
> Confirmed
> Status in ntp source package in Eoan:
> Confirmed
> Status in systemd source package in Eoan:
> Confirmed
> Status in ntp source package in Focal:
> Confirmed
> Status in systemd source package in Focal:
> Confirmed
>
> Bug description:
> Ubuntu 19.10's systemd package introduced /lib/systemd/
> timesyncd.
> systemd-
> installed. However, ntp.service has a Conflicts directive for
> systemd-
> start on boot. This breaks upgrades from < 19.10 to 19.10 for systems
> that have both ntp and systemd installed.
>
> Possible workarounds:
>
> - Uninstall ntp
> - Disable systemd-
>
> % lsb_release -rd
> Description: Ubuntu 19.10
> Release: 19.10
>
> % apt-cache policy systemd
> systemd:
> Installed: 242-7ubuntu3
> Candidate: 242-7ubuntu3
> Version table:
> *** 242-7ubuntu3 500
> 500 http://
> amd64 Packages
> 100 /var/lib/
>
> % apt-cache policy ntp
> ntp:
> Installed: 1:4.2.8p12+
> Candidate: 1:4.2.8p12+
> Version table:
> *** 1:4.2.8p12+
> 500 http://
> eoan/universe amd64 Packages
> 100 /var/lib/
>
> % dpkg -S
> /lib/systemd/
> systemd:
> /lib/systemd/
>
> % sudo systemctl status ntp
> ● ntp.service - Network Time Service
> Loaded: loaded (/lib/systemd/
> preset: enabled)
> Active: inactive (dead)
> Docs: man:ntpd(8)
>
> % sudo systemctl status systemd-
> ● systemd-
> Loaded: loaded (/lib/systemd/
> enabled; vendor preset: enabled)
> Drop-In: /lib/systemd/
> └─disable-
> Active: inactive (dead)
> Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
> Docs: man:systemd-
>
> Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
> Time Synchronization being skipped.
>
> To manage notifications about this bug go to:
> https:/
>