[kernel-bugs] [Bug 1176454] New: journald and udevd won't start due to status=228/SECCOMP
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 Bug ID: 1176454 Summary: journald and udevd won't start due to status=228/SECCOMP Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: opensuse@mike.franken.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Yesterday I updated one of my LEAP 15.2 machines. The machine rebootet into maintenance mode afterwards, but I wasn't able to do anything, because the keyboard also wasn't functional. There were error messages on the console regarding systemd-journald and systemd-udevd, which both failed to start. I was not able to recover from this situation, except by recovering the machine from the latest backup. Afterwards everything was back to normal - the machine came up as usual. I then retried the update and saw, that systemd-journald and systemd-udevd even refused to restart during this update. So I have a running machine now without those services, but I suppose, it won't reboot any more as before. Both services gave errors like this: Main PID: 18098 (code=exited, status=228/SECCOMP) -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 http://bugzilla.opensuse.org/show_bug.cgi?id=1176454#c1 --- Comment #1 from Michael Hirmke <opensuse@mike.franken.de> --- - working systemd version is systemd-234-lp152.31.4.1.x86_64 - not working version is systemd-234-lp152.31.7.1.x86_64 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 http://bugzilla.opensuse.org/show_bug.cgi?id=1176454#c2 --- Comment #2 from Oliver Schmidt <oliver.schmidt+suse@orlives.de> --- I'm affected by this as well after just updating my leap 15.2 server installation. Is it possible to roll the repositories back to a known-good state until this is figured out? Unfortunately I do not have an old Btrfs snapshot to roll back… -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 http://bugzilla.opensuse.org/show_bug.cgi?id=1176454#c4 Oliver Schmidt <oliver.schmidt+suse@orlives.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |opensuse@mike.franken.de Flags| |needinfo?(opensuse@mike.fra | |nken.de) --- Comment #4 from Oliver Schmidt <oliver.schmidt+suse@orlives.de> --- @Michael Hirmke: Some people in IRC didn't have issues with systemd-234-lp152.31.7.1, but I do as well have an unbootable system right now. A quick look at my logs suggests that (only?) systems running lvm are affected by this, are you using lvm? The folks without problems in IRC didn't use lvm. @Marcus Meissner: Yes, I did have the security repo enabled as well. But disabling and dist-upgrading from the main OSS repo doesn't trivially fix things, as for some reasons zypper wants to install a bunch of -mini packages and is looking for `this-is-only-for-build-envs` which obviously is not available, see attached screenshot. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 http://bugzilla.opensuse.org/show_bug.cgi?id=1176454#c5 --- Comment #5 from Oliver Schmidt <oliver.schmidt+suse@orlives.de> --- Created attachment 841639 --> http://bugzilla.opensuse.org/attachment.cgi?id=841639&action=edit screenshot of a conflict message after zypper dup I currently can only access my system via VNC, so no copy-past possible -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 http://bugzilla.opensuse.org/show_bug.cgi?id=1176454#c6 --- Comment #6 from Oliver Schmidt <oliver.schmidt+suse@orlives.de> --- Created attachment 841640 --> http://bugzilla.opensuse.org/attachment.cgi?id=841640&action=edit screenshot of systemd-udevd error messages at boot -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 http://bugzilla.opensuse.org/show_bug.cgi?id=1176454#c7 --- Comment #7 from Oliver Schmidt <oliver.schmidt+suse@orlives.de> --- As seen in the attached screenshot, a dist-upgrade with the security repo disabled and resolving the conflicts in a way that no -mini package gets installed still doesn't result in a booting system. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 http://bugzilla.opensuse.org/show_bug.cgi?id=1176454#c8 --- Comment #8 from Oliver Schmidt <oliver.schmidt+suse@orlives.de> --- Okay, ignore the last attachment, I just used a wrong zypper syntax. Workaround that fixed my system: 1. chroot into the system, make sure /boot is mounted as well 2. downgrade systemd to last known working version: `zypper in --oldpackage --allow-downgrade systemd-234-lp152.31.4.1` 3. `mkinitrd` 4. reboot That fixed it for me, for now I have added a lock on systemd to prevent this from happening again as long as the core issue is still here. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 http://bugzilla.opensuse.org/show_bug.cgi?id=1176454#c9 --- Comment #9 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Oliver Schmidt from comment #8)
Okay, ignore the last attachment, I just used a wrong zypper syntax.
Workaround that fixed my system: 1. chroot into the system, make sure /boot is mounted as well 2. downgrade systemd to last known working version: `zypper in --oldpackage --allow-downgrade systemd-234-lp152.31.4.1` 3. `mkinitrd` 4. reboot
That fixed it for me, for now I have added a lock on systemd to prevent this from happening again as long as the core issue is still here.
Yep, this is exactly my workaround. During the first attempt I forgot to run mkinitrd, therefore it failed. The second time I ran mkinitrd and it worked as expected. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 http://bugzilla.opensuse.org/show_bug.cgi?id=1176454#c10 --- Comment #10 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Marcus Meissner from comment #3)
do you have just thhe regular repositories enabled, or perhaps also the "security" repository?
I had the security repo active, yes. Therefore libseccomp2 version 2.5.0 got installed. But even disabling this repo and reinstalling libseccomp2 2.4.1 and all dependent packages didn't solve the problem. Probably I forgot something? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 http://bugzilla.opensuse.org/show_bug.cgi?id=1176454#c11 --- Comment #11 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Oliver Schmidt from comment #4)
@Michael Hirmke: Some people in IRC didn't have issues with systemd-234-lp152.31.7.1, but I do as well have an unbootable system right now.
A quick look at my logs suggests that (only?) systems running lvm are affected by this, are you using lvm? The folks without problems in IRC didn't use lvm.
No, I don't use lvm at all. This machine uses a sas hardware raid 1 for the boot and root partitons. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 http://bugzilla.opensuse.org/show_bug.cgi?id=1176454#c12 Michael Hirmke <opensuse@mike.franken.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME Flags|needinfo?(opensuse@mike.fra | |nken.de) | --- Comment #12 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Michael Hirmke from comment #10)
(In reply to Marcus Meissner from comment #3)
do you have just thhe regular repositories enabled, or perhaps also the "security" repository?
I had the security repo active, yes. Therefore libseccomp2 version 2.5.0 got installed. But even disabling this repo and reinstalling libseccomp2 2.4.1 and all dependent packages didn't solve the problem. Probably I forgot something?
Uhm, it seems to work now!?! I ran zypper up again, systemd & co were installed and udevd and journald restarted without a problem after the update. On reboot no errors occured and the system is running perfectly afterwards. So it seems, as if some remnant from the newer libseccomp2 caused the problem, but has vanished now. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176454 http://bugzilla.opensuse.org/show_bug.cgi?id=1176454#c13 Oliver Schmidt <oliver.schmidt+suse@orlives.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WORKSFORME |INVALID --- Comment #13 from Oliver Schmidt <oliver.schmidt+suse@orlives.de> --- For me it also works now after removing the "security" repo and regenerating the initramfs. Apparently this was the result of carelessly mixing system libraries from different repos, so I'd count this as a user error. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com