Bug#1080427: systemd fails to upgrade or respond, indicating a timeout error

Luca Boccassi bluca at debian.org
Tue Oct 8 22:03:47 BST 2024


Control: close -1

On Tue, 3 Sep 2024 20:43:22 +0200 "Petter L. H. Eide" <petter at eide.biz>
wrote:
> Package: systemd
> Version: 256.5-2
> Severity: important
> 
> Dear Maintainer,
> 
> When attempting to upgrade systemd, it fails with the following error
> message:
> 
> x at splendid:~$ sudo apt install --fix-broken
> Summary:
>   Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 91
>   3 not fully installed or removed.
>   Space needed: 0 B / 1550 GB available
> 
> Setting up systemd (256.5-2) ...
> Failed to retrieve unit state: Failed to activate service
> 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
> Failed to get properties: Failed to activate service
> 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
> dpkg: error processing package systemd (--configure):
>  installed systemd package post-installation script subprocess
returned
> error exit status 1
> dpkg: dependency problems prevent configuration of libpam-
systemd:amd64:
>  libpam-systemd:amd64 depends on systemd (= 256.5-2); however:
>   Package systemd is not configured yet.
> 
> dpkg: error processing package libpam-systemd:amd64 (--configure):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of libnss-
systemd:amd64:
>  libnss-systemd:amd64 depends on systemd (= 256.5-2); however:
>   Package systemd is not configured yet.
> 
> dpkg: error processing package libnss-systemd:amd64 (--configure):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  systemd
>  libpam-systemd:amd64
>  libnss-systemd:amd64
> Error: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> I see it is reporting issues in kernel log:
> x at splendid:~$ sudo dmesg | grep systemd | tail
> [1206807.222886] systemd-journald[598]: Failed to send WATCHDOG=1
> notification message: Transport endpoint is not connected
> [1206896.972072] systemd-journald[598]: Failed to send WATCHDOG=1
> notification message: Transport endpoint is not connected
> [1206987.220916] systemd-journald[598]: Failed to send WATCHDOG=1
> notification message: Transport endpoint is not connected
> [1207076.970031] systemd-journald[598]: Failed to send WATCHDOG=1
> notification message: Transport endpoint is not connected
> [1207167.219158] systemd-journald[598]: Failed to send WATCHDOG=1
> notification message: Transport endpoint is not connected
> [1207256.968271] systemd-journald[598]: Failed to send WATCHDOG=1
> notification message: Transport endpoint is not connected
> [1207347.217466] systemd-journald[598]: Failed to send WATCHDOG=1
> notification message: Transport endpoint is not connected
> [1207436.966581] systemd-journald[598]: Failed to send WATCHDOG=1
> notification message: Transport endpoint is not connected
> [1207526.965544] systemd-journald[598]: Failed to send WATCHDOG=1

D-Bus appears to be non-functional on your system. That is not a setup
that can be supported, sorry. Either reboot or reinstall, but there's
nothing we can do in the systemd package I'm afraid.



More information about the Pkg-systemd-maintainers mailing list