Bug#1088401: systemd 257~rc2-3 fails

[Elimork Bald]

Package: systemd

Hi!
I assume it's the systemd because after downgrading my systemd packages to 256.7-3, the systems works fine.

In essence, after "apt-get dist-upgrade" that pulled the 257~rc2-3 systemd packages, after reboot, the systemd struggles to deploy its services, failing with errors like this:

2024-11-27T18:02:52+01:00 host1 systemd[1]: Starting systemd-logind.service - User Login Management...
2024-11-27T18:02:52+01:00 host1 (d-logind)[1355]: systemd-logind.service: Failed to set up special execution directory in /run: No space left on device
2024-11-27T18:02:52+01:00 host1 (d-logind)[1355]: systemd-logind.service: Failed at step RUNTIME_DIRECTORY spawning /usr/lib/systemd/systemd-logind: No space left on device
2024-11-27T18:02:52+01:00 host1 systemd[1]: systemd-logind.service: Main process exited, code=exited, status=233/RUNTIME_DIRECTORY
2024-11-27T18:02:52+01:00 host1 systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
2024-11-27T18:02:52+01:00 host1 systemd[1]: Failed to start systemd-logind.service - User Login Management.
2024-11-27T18:02:52+01:00 host1 systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 1.

2024-11-27T18:02:53+01:00 host1 systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
2024-11-27T18:02:53+01:00 host1 (sshd)[1616]: ssh.service: Failed to set up special execution directory in /run: No space left on device
2024-11-27T18:02:53+01:00 host1 (sshd)[1616]: ssh.service: Failed at step RUNTIME_DIRECTORY spawning /usr/sbin/sshd: No space left on device
2024-11-27T18:02:53+01:00 host1 systemd[1]: ssh.service: Control process exited, code=exited, status=233/RUNTIME_DIRECTORY
2024-11-27T18:02:53+01:00 host1 systemd[1]: ssh.service: Failed with result 'exit-code'.
2024-11-27T18:02:53+01:00 host1 systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
2024-11-27T18:02:53+01:00 host1 systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1.

That is not little. User is left with a single terminal, and no desktop.

But after downgrade like this:

dpkg: warning: downgrading libnss-systemd:amd64 from 257~rc2-3 to 256.7-3
(Reading database ... 344060 files and directories currently installed.)
Preparing to unpack libnss-systemd_256.7-3_amd64.deb ...
Unpacking libnss-systemd:amd64 (256.7-3) over (257~rc2-3) ...
dpkg: warning: downgrading libpam-systemd:amd64 from 257~rc2-3 to 256.7-3
Preparing to unpack libpam-systemd_256.7-3_amd64.deb ...
Unpacking libpam-systemd:amd64 (256.7-3) over (257~rc2-3) ...
Preparing to unpack libsystemd-dev_256.7-3_amd64.deb ...
Unpacking libsystemd-dev:amd64 (256.7-3) over (256.7-3) ...
Preparing to unpack libsystemd-shared_256.7-3_amd64.deb ...
Unpacking libsystemd-shared:amd64 (256.7-3) over (256.7-3) ...
Preparing to unpack libsystemd0_256.7-3_amd64.deb ...
Unpacking libsystemd0:amd64 (256.7-3) over (256.7-3) ...
Preparing to unpack systemd-cryptsetup_256.7-3_amd64.deb ...
Unpacking systemd-cryptsetup (256.7-3) over (256.7-3) ...
dpkg: warning: downgrading systemd-sysv from 257~rc2-3 to 256.7-3
Preparing to unpack systemd-sysv_256.7-3_amd64.deb ...
Unpacking systemd-sysv (256.7-3) over (257~rc2-3) ...
dpkg: warning: downgrading systemd-timesyncd from 257~rc2-3 to 256.7-3
Preparing to unpack systemd-timesyncd_256.7-3_amd64.deb ...
Unpacking systemd-timesyncd (256.7-3) over (257~rc2-3) ...
dpkg: warning: downgrading systemd from 257~rc2-3 to 256.7-3
Preparing to unpack systemd_256.7-3_amd64.deb ...
Unpacking systemd (256.7-3) over (257~rc2-3) ...
Setting up libsystemd-shared:amd64 (256.7-3) ...
Setting up libsystemd0:amd64 (256.7-3) ...
Setting up systemd-cryptsetup (256.7-3) ...
Setting up systemd (256.7-3) ...
Installing new version of config file /etc/systemd/logind.conf ...
Installing new version of config file /etc/systemd/sleep.conf ...
/usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path "/run/lock", ignoring.
Setting up libnss-systemd:amd64 (256.7-3) ...
Setting up libsystemd-dev:amd64 (256.7-3) ...
Setting up systemd-sysv (256.7-3) ...
Setting up systemd-timesyncd (256.7-3) ...
systemd-time-wait-sync.service is a disabled or a static unit not running, not starting it.
systemd-timesyncd.service is a disabled or a static unit not running, not starting it.
Setting up libpam-systemd:amd64 (256.7-3) ...
Processing triggers for libc-bin (2.40-3) ...
Processing triggers for man-db (2.13.0-1) ...
Processing triggers for dbus (1.14.10-6) ...
Processing triggers for shared-mime-info (2.4-5+b1) ...

and after reboot, the systemd deploys its services fine.

Regards!

Elimork