Forums

Resolved
0 votes
Error: Multilib version problems found. nss-softokn-freebl

Hi all

I'm trying to update the server and i'm running into this error message, i'm not sure what to do, i'm guessing its a version conflict based on the source (repo) of the library. I Have the extra repos enabled.

i'm wondering if ayone else is seeing this problem. I'm not sure what version to keep so i'm asking the forum for advice. The proper command to fix the issue would be helpful as well

I've searched the forum and found this issue, however, i'm not sure the solutions applies, I'm on version 7.2 and the issue was reported on 6.6

So, here is the complete error message:


Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:

1. You have an upgrade for nss-softokn-freebl which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of nss-softokn-freebl of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude nss-softokn-freebl.otherarch ... this should give you an error
message showing the root cause of the problem.

2. You have multiple architectures of nss-softokn-freebl installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.

3. You have duplicate versions of nss-softokn-freebl installed already.
You can use "yum check" to get yum show these errors.

...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).

Protected multilib versions: nss-softokn-freebl-3.16.2.3-14.2.el7_2.x86_64 != nss-softokn-freebl-3.16.2.3-13.el7_1.i686
Monday, May 02 2016, 01:04 PM
Share this post:

Accepted Answer

Monday, May 02 2016, 01:24 PM - #Permalink
Resolved
1 votes
I just had this too on my home server..my resolution:
yum --enablerepo=* upgrade  nss-softokn-freebl
yum upgrade


B
The reply is currently minimized Show
Responses (5)
  • Accepted Answer

    Monday, May 02 2016, 09:16 PM - #Permalink
    Resolved
    0 votes
    Ok, I got confused there and I couldn't find any relavent packages to test against. Presumably grep is doing a regex match then? I did not realise it would do that without an explicit switch.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, May 02 2016, 07:57 PM - #Permalink
    Resolved
    0 votes
    Shouldn't it be:
    rpm -qa | grep i686


    The i.36 catches both i386 and i686 packages. 99% of the time it will be i686, but I just happened to be recently playing around with a Quickbooks i386 RPM :-)
    The reply is currently minimized Show
  • Accepted Answer

    Monday, May 02 2016, 07:14 PM - #Permalink
    Resolved
    0 votes
    Thanks for the specifics Pete.

    In my case, it was the SpiderOak library that I installed...I can see what happens....if you 'wget' the file, it pulls down the 32bit one from the URL on the host server. I didn't notice.

    To permanently resolve my issue, I removed the 32bit SpiderOak package and deps:

    yum remove SpiderOak nss-softokn-freeb glibc-2.17-106.el7_2.4.i686


    And made sure I downloaded the 64bit package and 'yum localinstall' that one.

    YMMV depending on what 32bit package you installed...if it was SpiderOak, you can follow exactly the same procedure.

    All good now.

    B.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, May 02 2016, 07:01 PM - #Permalink
    Resolved
    0 votes
    Peter Baldwin wrote:
    To check what 32-bit packages are installed on the system, run:
    rpm -qa | grep i.86

    Shouldn't it be:
    rpm -qa | grep i686
    The reply is currently minimized Show
  • Accepted Answer

    Monday, May 02 2016, 06:46 PM - #Permalink
    Resolved
    0 votes
    Do you have 32-bit packages installed? ClearOS itself no longer carries those packages ... just way too many issues happen when installing 32-bit items on a 64-bit box. It's 2016, there's no excuse for 32-bitness on a server! However, ClearOS used to map directly to CentOS repos and those *do* carry 32-bit packages. If you need to have 32-bit package installed, you will now need to have the CentOS repos enabled to upgrade:

    yum --enablerepo=centos-unverified,centos-updates-unverified upgrade nss-softokn-freebl


    The centos-unverified and centos-updates-unverified repos are direct links to CentOS repositories. The vast majority of the time, you can safely upgrade with these repos enabled, but from time to time (once or twice a year year), there is an unwanted update upstream.

    To check what 32-bit packages are installed on the system, run:

    rpm -qa | grep i.86
    The reply is currently minimized Show
Your Reply