Your message dated Sun, 28 Mar 2021 04:33:09 +0200
with message-id <[email protected]>
and subject line Re: Bug#980080: Failed to read server status: Transport
endpoint is not connected
has caused the Debian Bug report #980080,
regarding Failed to read server status: Transport endpoint is not connected
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
980080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980080
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 247.2-4
I do not know how my host got into this state
root@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.
Regards
Harri
--- End Message ---
--- Begin Message ---
On Thu, 21 Jan 2021 11:49:16 +0100 Harald Dunkel
<[email protected]> wrote:
Log file is attached.
As you can see, Docker is involved. AFAICT that was Docker version
5:20.10.2~3-0~debian-buster, provided by upstream as a Debian package.
The host was on Sid.
In the meantime this host has been reconfigured to run Kubernetes without
Docker (WIP).
Since we can't really do much with the existing information, let's close
this issue at this point, given that the host was reconfigured.
If you still run into this issue in the future, please reopen the bug
report.
Regards,
Michael
--- End Message ---
