Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)
Control: found -1 249.7-1 Control: severity -1 important Am 12.01.22 um 18:20 schrieb Christian Weeks: I don't see anything in the journal, I've had a fairly long look. I do not have the coredump utility installed. As I have mentioned, rebooting fixed whatever caused the problem during the upgrade, so I have no idea how I can help you further. In looking at my running system since, I notice that systemd isn't defaulting to running, so I guess the problem was actually that dbus was failing to activate systemd properly, during the upgrade. I have found a core file, but it's dated from 10 days ago, not today, which is weird. There was no activity on the computer at the time, I believe, and this went unnoticed, perhaps for 10 days?! As said, systemd freezes execution when it crashes. If PID 1 actually crashed, the kernel would panic and you'd notice :-) Jan 2 10:14:48 cheesypuffs kernel: [336844.954825] systemd[1]: segfault at 18 ip 55bd29c926ea sp 7ffdcd0c56c8 error 4 in systemd[55bd29c38000+d9000] ls -l /core -rw--- 1 root root 22482944 Jan 2 10:14 /core I can share this core file with you if you wish (how?), though perhaps it's not so related to the upgrade anymore? Given the timestamps match, it's pretty certain, that the core file belongs to the segfault. It also shows that PID 1 crashing is not actually affecting the running services. As long as you don't interact with systemd (e.g. via systemctl), your system should continue to run fine. I'm thus downgrading the severity. As it is not actually related to the upgrade, I'm marking it as found in 249.7-1. You can attach the core file to the bug report (gzipped) or mail it to me directly. I will try to see if a backtrace reveals something. Michael OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)
Processing control commands: > found -1 249.7-1 Bug #1003611 [systemd] systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable Marked as found in versions systemd/249.7-1. > severity -1 important Bug #1003611 [systemd] systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable Severity set to 'important' from 'critical' -- 1003611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)
I don't see anything in the journal, I've had a fairly long look. I do not have the coredump utility installed. As I have mentioned, rebooting fixed whatever caused the problem during the upgrade, so I have no idea how I can help you further. In looking at my running system since, I notice that systemd isn't defaulting to running, so I guess the problem was actually that dbus was failing to activate systemd properly, during the upgrade. I have found a core file, but it's dated from 10 days ago, not today, which is weird. There was no activity on the computer at the time, I believe, and this went unnoticed, perhaps for 10 days?! Jan 2 10:14:48 cheesypuffs kernel: [336844.954825] systemd[1]: segfault at 18 ip 55bd29c926ea sp 7ffdcd0c56c8 error 4 in systemd[55bd29c38000+d9000] ls -l /core -rw--- 1 root root 22482944 Jan 2 10:14 /core I can share this core file with you if you wish (how?), though perhaps it's not so related to the upgrade anymore? Christian On Wed, 2022-01-12 at 18:01 +0100, Michael Biebl wrote: > Control: tags -1 + moreinfo > > Hello, > > systemd freezes execution when it crashes (you should see a > corresponding log message in the journal). > > For this bug report to be actionable, we will need at the very least a > backtrace of the crash. > In case you had systemd-coredump installed, coredumpctl should show you. > Or maybe you still have a core file in /. > > > Regards, > Michael >
Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)
Control: tags -1 + moreinfo Hello, systemd freezes execution when it crashes (you should see a corresponding log message in the journal). For this bug report to be actionable, we will need at the very least a backtrace of the crash. In case you had systemd-coredump installed, coredumpctl should show you. Or maybe you still have a core file in /. Regards, Michael OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)
Processing control commands: > tags -1 + moreinfo Bug #1003611 [systemd] systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable Added tag(s) moreinfo. -- 1003611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)
The reboot fixed the issue - I now have a working computer again, though getting to a reboot was a bit painful. > systemctl reboot Failed to reboot system via logind: Connection timed out Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for details. It is possible to perform action directly, see discussion of --force --force in man:systemctl(1). > systemctl reboot --force Failed to execute operation: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) It is possible to perform action directly, see discussion of --force --force in man:systemctl(1). > systemctl reboot --force --force On Wed, 2022-01-12 at 15:36 +, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1003611: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003611. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian systemd Maintainers > > If you wish to submit further information on this problem, please > send it to 1003...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. >
