Public bug reported:
Several days ago an ubuntu 18.04 in ec2 env updated systemd and udev to
237-3ubuntu10.31
This caused systemd to segfault and stop receiving any systemctl command (they
timeout).
[ 198.482652] systemd[1]: segfault at 50 ip 00005630ddd60200 sp
00007ffc9c3ea890 error 4 in systemd (deleted)[5630ddcc1000+14e000]
[ 278.664729] systemd-journald[451]: Failed to send WATCHDOG=1 notification
message: Connection refused
[ 368.462136] systemd-journald[451]: Failed to send WATCHDOG=1 notification
message: Transport endpoint is not connected
[ 458.496689] systemd-journald[451]: Failed to send WATCHDOG=1 notification
message: Transport endpoint is not connected
I downgraded to 237-3ubuntu10.29 to no avail.
Then I downgraded to 237-3ubuntu10:
apt install udev=237-3ubuntu10 systemd=237-3ubuntu10 systemd-sysv=237-3ubuntu10
libsystemd0:amd64=237-3ubuntu10 libudev1:amd64=237-3ubuntu10
libnss-systemd:amd64=237-3ubuntu10
and that did not help either.
The machine is unusable at the moment.
Attaching coredump of systemd (version 237-3ubuntu10.31)
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852903
Title:
systemd Caught <SEGV>, dumped core
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852903/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
