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).
Regards
Harri
kern.log.t
Am 19.01.2021 um 12:11 schrieb Harald Dunkel:
AFAICS the host ran into OOM.
Hm, not sure if we can really do anything about that.
So it's likely that somewhere we failed to allocate memory. This could
be in dbus, systemd or any of the libraries we use.
Did the kernel OOM-killer kick in and the
AFAICS the host ran into OOM.
Regards
Harri
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@srvl065:~# systemctl status
Failed to read server status: Transport endpoint is not connected
but AFAICT this is not supposed
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 ho
5 matches
Mail list logo
