Bug#980080: Failed to read server status: Transport endpoint is not connected
Michael Biebl
biebl at debian.org
Thu Jan 14 14:01:47 GMT 2021
Control: tags -1 + moreinfo
Am 14.01.21 um 08:32 schrieb Harald Dunkel:
> Package: systemd
> Version: 247.2-4
>
> I do not know how my host got into this state
>
> root at srvl065:~# systemctl status
> Failed to read server status: Transport endpoint is not connected
>
> but AFAICT this is not supposed to happen. Google doesn't provide a
> recovery procedure, i.e. this host is dead.
You should be able to (forcefully) reboot with
"systemctl reboot --force".
Before doing that, can you check (your journal) for error messages
regarding dbus or systemd.
(you can send me a journalctl -alb dump privately, if you are concerned
regarding sharing something convidential which should not go to a public
bug report)
Regards,
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20210114/fadc4104/attachment.sig>
More information about the Pkg-systemd-maintainers
mailing list