Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#62161 - [systemd] systemd-timesyncd fails to start after upgrading to v240

Attached to Project: Arch Linux
Opened by Bryan L. Gay (linuxninja) - Thursday, 28 March 2019, 02:30 GMT
Last edited by Christian Hesse (eworm) - Thursday, 25 April 2019, 12:15 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 16
Private No

Details

Description:
upstream requires distribution package maintainers to add an installation script to remove the rm /var/lib/systemd/timesync symlink due to a breaking change upgrading systemd to v240

Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

see: https://github.com/systemd/systemd/issues/11329

Steps to reproduce:
Install systemd v239, boot the system, then upgrade to systemd v240.
systemd-timesyncd will fail to start

execute `rm /var/lib/systemd/timesync` to remove the old symlink
restart systemd-timesyncd
new directory is successfully created by systemd-timesyncd and the service starts normally

additional discussion can be found here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918190
This is not a distribution-specific problem, but upstream has decided that packagers must take it upon themselves to fix when upgrading.

Since the cause and fix are well discussed and known, I will not attach logs.
This task depends upon

Closed by  Christian Hesse (eworm)
Thursday, 25 April 2019, 12:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  systemd 242.0-2
Comment by Kevin Dodd (Jesin) - Friday, 12 April 2019, 20:21 GMT
I just encountered the same problem after updating to 242 from 241. Removing the symlink fixed it.
Comment by Jeb Rosen (jebrosen) - Saturday, 13 April 2019, 00:05 GMT
I had the same issue going from 241.93-1 to 242.0-1. `rm /var/lib/systemd/timesync` fixed it.
Comment by Peter Buxton (somercet) - Sunday, 21 April 2019, 17:21 GMT
[2019-04-12 08:55] [ALPM] upgraded systemd (241.93-1 -> 242.0-1)

Rebooted today, also had to delete symlink to fix timesyncd
Comment by George (Vash63) - Tuesday, 23 April 2019, 15:58 GMT
Same problem upgrading to 242.0-1 today
Comment by AMM (amish) - Tuesday, 23 April 2019, 16:04 GMT
Debian did this in post install script:

if [ -L /var/lib/systemd/timesync ] ; then
rm /var/lib/systemd/timesync
rm -rf /var/lib/private/systemd/timesync
fi

Source:
https://salsa.debian.org/systemd-team/systemd/commit/b274b4ad5a4ba543c8c013fb71dacf2467030ddc
Comment by Shalygin Konstantin (k0ste) - Wednesday, 24 April 2019, 02:37 GMT
241 -> 242:

```
-- Reboot --
Apr 24 09:28:20 WorkStation systemd[1]: Starting Network Time Synchronization...
Apr 24 09:28:20 WorkStation systemd[489]: systemd-timesyncd.service: Failed to set up special execution directory in /var/lib: Not a directory
Apr 24 09:28:20 WorkStation systemd[489]: systemd-timesyncd.service: Failed at step STATE_DIRECTORY spawning /usr/lib/systemd/systemd-timesyncd: Not a directory
Apr 24 09:28:20 WorkStation systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=238/STATE_DIRECTORY
Apr 24 09:28:20 WorkStation systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Apr 24 09:28:20 WorkStation systemd[1]: Failed to start Network Time Synchronization.
Apr 24 09:28:20 WorkStation systemd[1]: systemd-timesyncd.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Apr 24 09:28:20 WorkStation systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 1.
Apr 24 09:28:20 WorkStation systemd[1]: Stopped Network Time Synchronization.
Apr 24 09:28:20 WorkStation systemd[1]: Starting Network Time Synchronization...
Apr 24 09:28:20 WorkStation systemd[500]: systemd-timesyncd.service: Failed to set up special execution directory in /var/lib: Not a directory
Apr 24 09:28:20 WorkStation systemd[500]: systemd-timesyncd.service: Failed at step STATE_DIRECTORY spawning /usr/lib/systemd/systemd-timesyncd: Not a directory
Apr 24 09:28:20 WorkStation systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=238/STATE_DIRECTORY
Apr 24 09:28:20 WorkStation systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Apr 24 09:28:20 WorkStation systemd[1]: Failed to start Network Time Synchronization.
Apr 24 09:28:20 WorkStation systemd[1]: systemd-timesyncd.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Apr 24 09:28:20 WorkStation systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 2.
Apr 24 09:28:20 WorkStation systemd[1]: Stopped Network Time Synchronization.
```

Solution from Jeb fixed this issue.
Comment by Shalygin Konstantin (k0ste) - Wednesday, 24 April 2019, 02:39 GMT
https://github.com/systemd/systemd/commit/787a133f2d934d9cb01a50ee86ea5c51926c6ef8

I think this may be posted on Archlinux News main page.
Comment by Christian Hesse (eworm) - Thursday, 25 April 2019, 11:34 GMT
Fixed in SVN, this will be cleaned up on next package update.

Loading...