On Mon, 17 Dec 2018, Michael Biebl wrote: > > Control: severity -1 important > Control: tags -1 moreinfo > > Am 17.12.18 um 11:25 schrieb Cristian Ionescu-Idbohrn: > > > | systemd[1]: Caught <SEGV>, dumped core as pid 2097. > > Please try to get a backtrace following > https://wiki.debian.org/HowToGetABacktrace
Sorry, too late :( As I mentioned, ssh login failed and phisical console was far away. I needed to get that box alive again. Got it rebooted. Isn't this: ,---- | 2018-12-16 17:16:08 host:6665 0,1210,543999638601,-;systemd[1]: segfault at ffffffffffffffe0 ip 00007f2d93990647 sp 00007ffcabd85028 error 5 | 2018-12-16 17:16:08 host:6665 4,1211,543999661307,c; in libc-2.28.so[7f2d93856000+148000] `---- sufficient? It reports the origin of the segfault is libc 2.28, which was upgraded from 2.27 behind systemd's back: -libc-bin 2.27-8 amd64 -libc-dev-bin 2.27-8 amd64 -libc-l10n 2.27-8 all -libc6 2.27-8 amd64 -libc6-dbg 2.27-8 amd64 -libc6-dev 2.27-8 amd64 -libc6-dev-i386 2.27-8 amd64 -libc6-dev-x32 2.27-8 amd64 -libc6-i386 2.27-8 amd64 -libc6-x32 2.27-8 amd64 +libc-bin 2.28-2 amd64 +libc-dev-bin 2.28-2 amd64 +libc-l10n 2.28-2 all +libc6 2.28-2 amd64 +libc6-dbg 2.28-2 amd64 +libc6-dev 2.28-2 amd64 +libc6-dev-i386 2.28-2 amd64 +libc6-dev-x32 2.28-2 amd64 +libc6-i386 2.28-2 amd64 +libc6-x32 2.28-2 amd64 There could have been a daemon-reexec too, at some point. I don't recall. Cheers, -- Cristian