[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
Hmm thanks Raphaël. So files were still around that were unowned, that really should not happen. Thanks for the exact file names. The files you had in your case were part of libseccomp2 2.3.1-2.1ubuntu4 which is what Ubuntu had in Bionic-release. libseccomp2 | 2.3.1-2.1ubuntu4 | bionic | But before you'd be able to upgrade to Focal (do-release-upgrade will otherwise block) that would even in Bionic be upgraded to 2.4.3-1ubuntu3.18.04.3 libseccomp2 | 2.4.3-1ubuntu3.18.04.3 | bionic-security | libseccomp2 | 2.4.3-1ubuntu3.18.04.3 | bionic-updates | On that upgrade these files would vanish. I've taken a Bionic system, downgraded to 2.3.1-2.1ubuntu4 and from there upgraded the package. The files went away as one would expect: root@b:~# ll /lib/x86_64-linux-gnu/libseccomp.so* lrwxrwxrwx 1 root root 19 Mar 1 2018 /lib/x86_64-linux-gnu/libseccomp.so.2 -> libseccomp.so.2.3.1 -rw-r--r-- 1 root root 280776 Mar 1 2018 /lib/x86_64-linux-gnu/libseccomp.so.2.3.1 root@b:~# apt install libseccomp2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: libseccomp2 1 upgraded, 0 newly installed, 0 to remove and 28 not upgraded. Need to get 42.0 kB of archives. After this operation, 29.7 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libseccomp2 amd64 2.4.3-1ubuntu3.18.04.3 [42.0 kB] Fetched 42.0 kB in 0s (312 kB/s) (Reading database ... 43328 files and directories currently installed.) Preparing to unpack .../libseccomp2_2.4.3-1ubuntu3.18.04.3_amd64.deb ... Unpacking libseccomp2:amd64 (2.4.3-1ubuntu3.18.04.3) over (2.3.1-2.1ubuntu4) ... Setting up libseccomp2:amd64 (2.4.3-1ubuntu3.18.04.3) ... Processing triggers for libc-bin (2.27-3ubuntu1.2) ... root@b:~# ll /lib/x86_64-linux-gnu/libseccomp.so* lrwxrwxrwx 1 root root 19 Jun 29 12:52 /lib/x86_64-linux-gnu/libseccomp.so.2 -> libseccomp.so.2.4.3 -rw-r--r-- 1 root root 309456 Jun 29 12:52 /lib/x86_64-linux-gnu/libseccomp.so.2.4.3 Do you have any chance (backup, snapshot or anything) to check which package (if any) owned these files on your Bionic system before upgrade? Furthermore from your system it might be interesting to get /var/log/dpkg.log* attached here. Not sure one can find something in there, but we could track exactly what happened to your libseccomp2 in the past - maybe that reconstruction helps to find how/why these files got left on your disk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
These files didn't belong to any package (anymore?). Here are the files I removed: - /lib/x86_64-linux-gnu/libseccomp.so.2.3.1 - /lib/x86_64-linux-gnu/libseccomp.so.2 (link to the previous file) - /usr/lib/x86_64-linux-gnu/libseccomp.so.2.3.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
I'm in the same case as Joi: I went from Ubuntu 16.04 to Ubuntu 18.04 to Ubuntu 20.04. Removing libsecomp libraries in /lib and the old one in /usr/lib (version 2.3) allowed the system to boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
Hi Joi, thanks for the extra data, I still can't think of a case to create this. Looking forward to what you find checking this in more detail. When in the error case could you look around which seccomp the system still has around? For example via: $ ls -laF /lib/x86_64-linux-gnu/libseccomp* /usr/lib/x86_64-linux-gnu/libseccomp* $ dpkg -S /lib/x86_64-linux-gnu/libseccomp* /usr/lib/x86_64-linux-gnu/libseccomp* $ apt-cache policy '*libseccomp*' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
I've just encountered this issue myself, on a VM that started life as Ubuntu 16.04, do-release-upgrade to 18.04, then to 20.04, and now it fails to boot with a similar error: /lib/systemd/libsystemd- shared-245.so: undefined symbol: seccomp_api_get The only non-Ubuntu-standard stuff on this VM is some perl modules installed via CPAN, and none of those touch anything to do with Systemd, so I'm not sure why this is happening. I did see a post-install upgrade issue with the rkhunter package failing to find /usr/bin/egrep, but I ignored that issue and continued. I'm going to rollback, look for the lib involved, and see if I can remove it before retrying the do-release-upgrade -d to 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
Moving back to incomplete as stated by @paelzer. ** Changed in: libseccomp (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libseccomp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
Hi, even Bionic which you upgraded from would have been /lib/x86_64-linux-gnu/libseccomp.so.2.4.1 2.2 was last available in libseccomp2 | 2.2.3-2ubuntu1~ubuntu14.04.1 | trusty-backports | amd64, arm64, armhf, i386, powerpc, ppc64el libseccomp2 | 2.2.3-3ubuntu3 | xenial | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x And it would have been removed in Bionic a long time ago. Unless this was a file not out of the Ubuntu Archive in which case I'm not sure what we could do to help. I'll mark it incomplete and I'm glad that you were able to resolve it for yourself. Is there anything out of this you'd think that Ubuntu as an OS could do better - I see no opportunity as it seems not to be caused by the packages provided. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
After trying to roll forward again I saw the output from ldconfig /lib/x86_64-linux-gnu/libseccomp.so.2.2.0 is not a symbolic link Looks like I had duplicate versions of libseccomp2 lying around on my LD_LIBRARY_PATH dpkg -L libseccomp2 /usr/lib/x86_64-linux-gnu/libseccomp.so.2.4.3 So I deleted the ones in /lib/ and then upgraded systemd to the latest version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
This is something to do with linux 5 kernel api You need to manually downgrade systemd - well - that's what I did. when you boot with grub or refind - edit default entry and change the init=/bin/init to init=/bin/bash That will bypass systemd starting up and drop you straight into a shell. mount -o remount / mount /usr mount /var mount /dev/sdc1 /mnt dpkg -i /mnt/systemd_241-7~deb10u3_amd64.deb On a system that works or download a previous version somehow. dpkg -l systemd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii systemd245.5-2 amd64system and service manager root@leet:/home/wozza# apt-cache policy systemd systemd: Installed: 245.5-2 Candidate: 245.5-2 Version table: *** 245.5-2 500 500 http://ftp.iinet.net.au/debian/debian bullseye/main amd64 Packages 100 /var/lib/dpkg/status 241-7~deb10u3 500 500 http://ftp.iinet.net.au/debian/debian stable/main amd64 Packages root@leet:/home/wozza# apt-get download systemd=241-7~deb10u3 Get:1 http://ftp.iinet.net.au/debian/debian stable/main amd64 systemd amd64 241-7~deb10u3 [3,495 kB] Fetched 3,495 kB in 11s (321 kB/s) W: Download is performed unsandboxed as root as file '/home/wozza/systemd_241-7~deb10u3_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) root@leet:/home/wozza# ll systemd_241-7~deb10u3_amd64.deb -rw-r--r-- 1 root root 3495428 Jan 31 15:11 systemd_241-7~deb10u3_amd64.deb root@leet:/home/wozza# mount /dev/sdc1 /mnt root@leet:/home/wozza# cp systemd_241-7~deb10u3_amd64.deb /mnt/ root@leet:/home/wozza# cd /mnt/ root@leet:/mnt# mkdir unpack root@leet:/mnt# cd unpack/ root@leet:/mnt/unpack# dpkg-deb -R ../systemd_241-7~deb10u3_amd64.deb . worst comes to worse can copy the files across from unpack directory - good luck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs