Glibc Update

Yesterday glibc was updated to vs 2.,26. This apparently caused problems.

This update deposits a file: /etc/nsswitch.conf.rpmnew. After the update has taken place and before any reboots, this file must be copied over nsswitch.conf, viz:

cd /etc
sudo mv nsswitch.conf nsswitch.conf.old
sudo mv nsswitch.conf.rpmnew nsswitch.conf

That worked here.

2 Likes

Same issue here

https://forum3.openmandriva.org/t/something-in-auto-update-causes-system-to-not-boot/1407/18

Thanks for the hint with nsswitch.conf

And issue resolved by this?

Great!
This solved here.
:slight_smile:

@mandian @christopher_tanner can you guys please post your /etc/nsswitch.conf after applying this workaround ?

Here (1.3 KB) is the actual nsswitch.conf i.e the one provided by rpm, here (1.3 KB) is the old one, i.e. the one who causes the issue, and here (357 Bytes) is the diff. I added .txt extension to upload the files on this forum.

1 Like

I have the same.

So the nsswitch.conf file provided by glibc-2.26 is working, right ?

It is certainly working here.

I have reinstalled.
an ls -l .etc/nss returns

Blockquote-
rw-r–r-- 1 root root 1326 Sep 12 14:49 /etc/nsswitch.conf
-rw-r–r-- 1 root root 1326 Sep 12 14:49 /etc/nsswitch.conf.bak
-rw-r–r-- 1 root root 1337 Jul 16 09:14 /etc/nsswitch.conf.rpmsave
The contens of all the files are identical and are the one’s that cause the later version of glibc to fail.

Blockquote

This is after performing urpmi --auto-update
There was no libc in the update

Blockquote
rpm -qa | grep glibc
glibc-2.25-1-omv2015.0.x86_64

Blockquote

Everything appears to be working
Did the update fail because there was already a backup file?
I know normally one doesn’t overwrite config files on update but in this circustance…?

This is from the fixed box:
$ rpm -qa | grep glibc
glibc-2.26-4-omv2015.0.x86_64
glibc-devel-2.26-4-omv2015.0.x86_64

@TPG It looks so here.

This fix worked here on a computer that had had multiple boot attempts after the update. Obviously you have to access the broken system from ‘Live’ ISO or from another computer or another system if on a multi-boot computer to make the necessary adjustment.

@christopher_tanner I’m curious, how did you know to look for this? Is there some output in ‘urpmi --auto-update’ that tells us to look for a .rpmnew file or files?

At time of writing, update does not propose any glibc update. So urpmi --auto-update seems to be safe now.

To satisfy dependencies, the following packages are going to be installed:
(test only, installation will not be actually done)
 Package                        Version      Release       Dist  DEpoch Arch 
(medium "main_up")
 lib64dri-drivers               17.1.8       1             omv   2015.0 x86_64 
 lib64dri-drivers-intel         17.1.8       1             omv   2015.0 x86_64 
 lib64dri-drivers-nouveau       17.1.8       1             omv   2015.0 x86_64 
 lib64dri-drivers-radeon        17.1.8       1             omv   2015.0 x86_64 
 lib64dri-drivers-swrast        17.1.8       1             omv   2015.0 x86_64 
 lib64dri-drivers-virtio        17.1.8       1             omv   2015.0 x86_64 
 lib64dri-drivers-vmwgfx        17.1.8       1             omv   2015.0 x86_64 
 lib64egl1                      17.1.8       1             omv   2015.0 x86_64 
 lib64gbm1                      17.1.8       1             omv   2015.0 x86_64 
 lib64gl1                       17.1.8       1             omv   2015.0 x86_64 
 lib64glapi0                    17.1.8       1             omv   2015.0 x86_64 
 lib64mozjs185_1                1.85         21            omv   2015.0 x86_64 
 lib64mpfr4                     3.1.6        1             omv   2015.0 x86_64 
 lib64nss_myhostname2           234          2             omv   2015.0 x86_64 
 lib64systemd-devel             234          2             omv   2015.0 x86_64 
 lib64systemd0                  234          2             omv   2015.0 x86_64 
 lib64udev-devel                234          2             omv   2015.0 x86_64 
 lib64udev1                     234          2             omv   2015.0 x86_64 
 lib64vdpau-driver-r600         17.1.8       1             omv   2015.0 x86_64 
 lib64vdpau-driver-radeonsi     17.1.8       1             omv   2015.0 x86_64 
 lib64wayland-egl1              17.1.8       1             omv   2015.0 x86_64 
 lib64xatracker2                17.1.8       1             omv   2015.0 x86_64 
 systemd                        234          2             omv   2015.0 x86_64 
 systemd-bash-completion        234          2             omv   2015.0 x86_64 (suggested)
 systemd-zsh-completion         234          2             omv   2015.0 x86_64 (suggested)
 zsh                            5.3.1        1             omv   2015.0 x86_64 (suggested)
3.4MB of additional disk space will be used.
48MB of packages will be retrieved.
Proceed with the installation of the 26 packages? (Y/n) y

==

[ruru@omlx-1403 ~]$ rpm -qa|grep glibc
glibc-2.25-1-omv2015.0.x86_64
glibc-devel-2.25-1-omv2015.0.x86_64

A couple of things told me about it:

a) when you run urpmi --auto-update: as it installs glibc, rpm does state that nsswitch.conf.rpmnew is created.

b) I ran into this same situation on cooker and it took a couple of trys before I twigged to what was going on.

1 Like

Thanks.

Offending package removed. Closing thread.

Will inform everyone when new glibc package stack is available in new thread.

1 Like