[Touch-packages] [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 Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade Status in libseccomp package in Ubuntu: Incomplete Bug description: Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not possible. The error messages is: /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get [4.608900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 See also attached photograph of screen during boot. Upgrade followed steps from here: https://help.ubuntu.com/community/FocalUpgrades/Kubuntu With the excpetion that The -d flag was used for the do-release-upgrade: sudo do-release-upgrade -d -m desktop 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Prior to upgrade: Ubuntu 18.04.4 After upgrade (but never booted): Ubuntu (Kubuntu) 20.04 Note that Ubuntu had originally be installed, but kubuntu-desktop was recently installed to change to Kubuntu, but no booting problems were experienced before updating to 20.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Unknown -- Package version may have changed when upgrading to 20.04. 3) What you expected to happen Boot without kernel panic. 4) What happened instead Could not boot. Even selecting safe mode from grub could not boot. Had to restore system from backups. Will not attempt upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
I've done some more digging into the systemd package update issue. We have a number of Ubuntu 18.04 hosts, most of them are virtual machines running simple eth0 configurations under Hyper-V. All of those VMs updated the systemd package without issue. The only hosts which had issues after the systemd package upgrade were the two SuperMicros running bonded 10G interfaces. On both of those hosts, the bond defined in netplan seems to have lost its configuration during the systemd upgrade. There were multiple kern.log messages regarding the bond leaving one of its ports in a disabled state after the update. Both hosts logged this on the same second that dpkg.log shows the systemd package itself entering 'status installed', so I'm confident it was that systemd package rather than pam-systemd that followed several seconds later. I am still willing to provides logs and configurations if you tell me what you need to see. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces Status in systemd package in Ubuntu: Incomplete Bug description: Info: Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 2018). HP DL380 server I had this issue already twice in the past couple of months. After unattended upgrade of systemd my server's public IP address is removed from the interface. I statically configure the IP address using the interfaces file. I have opted out of the YML based network configuration. This is my apt history log: Start-Date: 2019-04-09 06:15:01 Commandline: /usr/bin/unattended-upgrade Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:07 Start-Date: 2019-04-09 06:15:12 Commandline: /usr/bin/unattended-upgrade Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:56 Start-Date: 2019-04-09 06:15:59 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:16:15 After that my server was unavailable from the Internet. When I logged in via out of band management and simply brought down and up the interface everything went back to normal. As said above this is the second time I had this issue. Last time it was unattended upgrades and it was systemd again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
I followed up with my coworker who originally built our two misbehaving boxes. He also ended up having to reboot the second box I left for him, to get the br01 bridge configuration back in working order. Simply running 'netplan apply' and restarting the systemd network service did not resolve it, but a full reboot did. We are using the default 18.04 netplan setup, we haven't reversed back to ifupdown like the other reporter. Both hosts lost their networking immediately after the systemd update was applied this morning, which installed version 237-3ubuntu10.19. I can delve through them to find any logs or config files you want. These are Supermicro rack mounts with dual 10G interfaces, built as headless servers, so no ubuntu-desktop or X11 is installed on them. We have sssd installed on these with the required pam customizations to configure sssd to live in our Active Directory environment. pam-auth- updated printed about local mods to common-* so it wasn't updating. Those are the only unusual outputs from this mornings unattended- upgrades-dpkg.log file. I can attach any logs or other files you care to view. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces Status in systemd package in Ubuntu: Incomplete Bug description: Info: Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 2018). HP DL380 server I had this issue already twice in the past couple of months. After unattended upgrade of systemd my server's public IP address is removed from the interface. I statically configure the IP address using the interfaces file. I have opted out of the YML based network configuration. This is my apt history log: Start-Date: 2019-04-09 06:15:01 Commandline: /usr/bin/unattended-upgrade Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:07 Start-Date: 2019-04-09 06:15:12 Commandline: /usr/bin/unattended-upgrade Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:56 Start-Date: 2019-04-09 06:15:59 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:16:15 After that my server was unavailable from the Internet. When I logged in via out of band management and simply brought down and up the interface everything went back to normal. As said above this is the second time I had this issue. Last time it was unattended upgrades and it was systemd again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
Two of our Ubuntu 18.04 hosts applied this update this morning and both dropped offline. They're both using netplan and have bonded interfaces. The bond layer was offline. I had to reboot to get the network stack running again. I left one host offline so the coworker who configured them can look it over later this morning. Two identical hosts did not apply this systemd update this morning and they're both still online. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces Status in systemd package in Ubuntu: Confirmed Bug description: Info: Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 2018). HP DL380 server I had this issue already twice in the past couple of months. After unattended upgrade of systemd my server's public IP address is removed from the interface. I statically configure the IP address using the interfaces file. I have opted out of the YML based network configuration. This is my apt history log: Start-Date: 2019-04-09 06:15:01 Commandline: /usr/bin/unattended-upgrade Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:07 Start-Date: 2019-04-09 06:15:12 Commandline: /usr/bin/unattended-upgrade Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:56 Start-Date: 2019-04-09 06:15:59 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:16:15 After that my server was unavailable from the Internet. When I logged in via out of band management and simply brought down and up the interface everything went back to normal. As said above this is the second time I had this issue. Last time it was unattended upgrades and it was systemd again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585614] Re: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
@adconrad As it happens, it did. I just came back to update my comment to say so and found your question. This suggests the libc6 update (not glibc, my server doesn't have glibc package installed) should have required a reboot? I don't recall if the server mentioned a reboot was required in the motd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1585614 Title: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Status in eglibc package in Ubuntu: Confirmed Bug description: This morning I applied the following updates to Ubuntu 12.04 webservers: The following packages are currently pending an upgrade: apt 0.8.16~exp12ubuntu10.27 apt-transport-https 0.8.16~exp12ubuntu10.27 apt-utils 0.8.16~exp12ubuntu10.27 libapache2-mod-php5 5.3.10-1ubuntu3.23 libapt-inst1.4 0.8.16~exp12ubuntu10.27 libapt-pkg4.12 0.8.16~exp12ubuntu10.27 php5-cli 5.3.10-1ubuntu3.23 php5-common 5.3.10-1ubuntu3.23 php5-curl 5.3.10-1ubuntu3.23 php5-dev 5.3.10-1ubuntu3.23 php5-gd 5.3.10-1ubuntu3.23 php5-mysql 5.3.10-1ubuntu3.23 php-pear 5.3.10-1ubuntu3.23 Apache fails to restart, siting error: apache2: Syntax error on line 212 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/php5.load: Cannot load /usr/lib/apache2/modules/libphp5.so into server: /lib/x86_64-linux- gnu/libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Into file /var/log/apache2/error.log Looks like I am trying to roll back all those php packages... Which I see several updates marked Security Update in the changelogs, thus checking the "security vulnerability" box as rolling back in this case is such. :-( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1585614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585614] Re: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
This change in libm.so has also broken the pam_mysql.so library, thus my vsftpd service is also broken. My nagios started alarming about this breaking around 6:30 am this morning, dpkg.log shows only 5 packages were updated in this morning's automatic update: man-db, libc-bin, libc6, and multiarch-support (all from amd64 arch.) The error in auth.log is: vsftpd: PAM unable to dlopen(pam_mysql.so): /lib/x86_64-linux-gnu/libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference. vsftpd: PAM adding faulty module: pam_mysql.so (I had to manually type the above, as MS hyperv can't do simple clipboard operations like Xen has managed for over a decade now. So please forgive any typos that might be there.) I don't think this is an apache or pam bug, as libm.so is provided by libc6. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1585614 Title: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Status in eglibc package in Ubuntu: Confirmed Bug description: This morning I applied the following updates to Ubuntu 12.04 webservers: The following packages are currently pending an upgrade: apt 0.8.16~exp12ubuntu10.27 apt-transport-https 0.8.16~exp12ubuntu10.27 apt-utils 0.8.16~exp12ubuntu10.27 libapache2-mod-php5 5.3.10-1ubuntu3.23 libapt-inst1.4 0.8.16~exp12ubuntu10.27 libapt-pkg4.12 0.8.16~exp12ubuntu10.27 php5-cli 5.3.10-1ubuntu3.23 php5-common 5.3.10-1ubuntu3.23 php5-curl 5.3.10-1ubuntu3.23 php5-dev 5.3.10-1ubuntu3.23 php5-gd 5.3.10-1ubuntu3.23 php5-mysql 5.3.10-1ubuntu3.23 php-pear 5.3.10-1ubuntu3.23 Apache fails to restart, siting error: apache2: Syntax error on line 212 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/php5.load: Cannot load /usr/lib/apache2/modules/libphp5.so into server: /lib/x86_64-linux- gnu/libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Into file /var/log/apache2/error.log Looks like I am trying to roll back all those php packages... Which I see several updates marked Security Update in the changelogs, thus checking the "security vulnerability" box as rolling back in this case is such. :-( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1585614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
