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
@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
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
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
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
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
6 matches
Mail list logo
