Red Hat Bugzilla – Bug 1477308
Installing new nss-softokn-freebl without updating nspr on a RHEL 7.3.0 system results in rpm and yum being non-functional
Last modified: 2018-05-16 16:19:18 EDT
Description of problem: The nss-softokn packaging does not have a requirement for a matching nspr package. As a result, the installation of the glibc.i686 package pulls in nss-softokn-freebl, but not the additionally required nspr version. Version-Release number of selected component (if applicable): nss-softokn-freebl-3.28.3-6.el7 How reproducible: Easily Steps to Reproduce: 1. Install a RHEL 7.3 system 2. yum install glibc.i686 3. rpm -qa Actual results: # rpm -qa error: Failed to initialize NSS library Expected results: # rpm -qa <Return RPM database contents> Additional info: Once the issue has been seen, the yum and rpm utilities are functionally broken. Manually loading the updated nspr library via LD_PRELOAD seems to resolve the condition temporarily, and can be used to update the nspr package manually.
Issue also presents itself as: # yum repolist error: Failed to initialize NSS library There was a problem importing one of the Python modules required to run yum. The error leading to this problem was: cannot import name ts Please install a package which provides this module, or verify that the module is installed correctly. It's possible that the above module doesn't match the current version of Python, which is: 2.7.5 (default, Aug 2 2016, 04:20:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-4)] If you cannot solve this problem yourself, please go to the yum faq at: http://yum.baseurl.org/wiki/Faq - Kyle Walker
So this is workaround for broken system. 1. Use wget, or any other way to get the needed nspr package from the repository. needed package: nspr-4.13.1-1.0.el7_3 2. get the nspr libraries out from rpm rpm2cpio nspr-4.13.1-1.0.el7_3.x86_64.rpm |cpio -imdv 3. copy them to /usr/lib64/ cp usr/lib64/* /usr/lib64/ This should solve the problem. Use the proper rpm for architecture of your system. And make sure you are hitting the right paths also.
The issue will happen only on systems that are updating nss-softokn-freebl alone and do not have https://rhn.redhat.com/errata/RHEA-2017-0460.html (nspr-4.13.1-1.0.el7_3) installed.
Guys, i am hitting the same problem on RHEL 7.2 and the solution mentioned above does not fix it. Any hints [root@mon-node1 tmp]# rpm2cpio nspr-4.13.1-1.0.el7_3.i686.rpm | cpio -imdv error: Failed to initialize NSS library ./usr/lib/libnspr4.so ./usr/lib/libplc4.so ./usr/lib/libplds4.so 555 blocks [root@mon-node1 tmp]# cp usr/lib/* /usr/lib64/ cp: overwrite ‘/usr/lib64/libnspr4.so’? y cp: overwrite ‘/usr/lib64/libplc4.so’? y cp: overwrite ‘/usr/lib64/libplds4.so’? y [root@mon-node1 tmp]# [root@mon-node1 tmp]# [root@mon-node1 tmp]# yum repolist There was a problem importing one of the Python modules required to run yum. The error leading to this problem was: libplc4.so: wrong ELF class: ELFCLASS32 Please install a package which provides this module, or verify that the module is installed correctly. It's possible that the above module doesn't match the current version of Python, which is: 2.7.5 (default, Oct 11 2015, 17:47:16) [GCC 4.8.3 20140911 (Red Hat 4.8.3-9)] If you cannot solve this problem yourself, please go to the yum faq at: http://yum.baseurl.org/wiki/Faq [root@mon-node1 tmp]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.2 (Maipo) [root@mon-node1 tmp]# uname -a Linux mon-node1 3.10.0-327.el7.x86_64 #1 SMP Thu Oct 29 17:29:29 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux [root@mon-node1 tmp]#
Just a guess - i686 vs. x86_64 architecture? Did you try with x86_64 rpm?
No, I have not, Could you help me with the correct package download link.
@Stanislav Zidek Thanks a lot, x86_64 rpm worked as expected.
We had a similar issue with a new 7.1 host. Initially the PRELOAD did not work. In order to work around this issue, we repulled the latest katello cert and installed that with --force with the LD_PRELOAD=./... hope this helps. Thanks, Dave
*** Bug 1476031 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0679