Error multilib version problems found

I use CentOS 6.4 When I tried to install libgcc with yum install libgcc.i686 I took following massages. Error: Multilib version problems found. This often means that the root cause is somet...

I use CentOS 6.4

When I tried to install libgcc with yum install libgcc.i686 I took following massages.

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 libgcc which is missing some
            dependency that another package requires. Yum is trying to
            solve this by installing an older version of libgcc 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 libgcc.otherarch ... this should give you an error
            message showing the root cause of the problem.
       
         2. You have multiple architectures of libgcc installed, but
            yum can only see an upgrade for one of those arcitectures.
            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 libgcc 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: libgcc-4.4.7-4.el6.i686 != libgcc-4.4.7-3.el6.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles –nodigest

How can I install libgcc.i686?

Yuri's user avatar

Yuri

2181 silver badge6 bronze badges

asked May 20, 2014 at 8:52

user1345414's user avatar

It seems your libgcc.x86_64 has a different version than the libgcc.i686 you are trying to install (4.4.7-3 vs. 4.4.7-4). Try to update the x86_64 lib together with the installation of the i686-lib:

yum install libgcc.x86_64 libgcc.i686

answered May 20, 2014 at 12:17

etagenklo's user avatar

etagenkloetagenklo

5,7741 gold badge25 silver badges31 bronze badges

1

I’ve hit this after interrupting yum update (during an ansible run in my case). After reading this thread I eventually fixed it with:

package-cleanup --cleandupes

Though before that I’d also tried running commands as @etagenklo suggested, and also tried:

yum-complete-transaction
yum-complete-transaction --cleanup-only
yum check                # report generally
package-cleanup --dupes  # report on duplicate packages in particular

answered Oct 17, 2018 at 7:46

Hamish Downer's user avatar

Hamish DownerHamish Downer

9,2806 gold badges37 silver badges50 bronze badges

I think it worth to mention because it was my issues check

/etc/yum.repos.d/*

and check if there is not used or unofficial source

answered Mar 24, 2018 at 0:08

Mohamed Abo Badawy's user avatar

How can we fix this error?

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 apr which is missing some
    dependency that another package requires. Yum is trying to
    solve this by installing an older version of apr 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 apr.otherarch ... this should give you an error
    message showing the root cause of the problem.

  2. You have multiple architectures of apr installed, but
    yum can only see an upgrade for one of those arcitectures.
    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 apr 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).

    Error:
    Protected multilib versions: apr-1.3.9-5.el6_2.i686 != apr-1.5.2-2.x86_64
    Protected multilib versions: apr-util-1.3.9-3.el6_0.1.i686 != apr-util-1.5.4-2.x86_64
    

Esa Jokinen's user avatar

Esa Jokinen

44.6k2 gold badges77 silver badges128 bronze badges

answered Jun 14, 2017 at 5:05

sam's user avatar

1

RedHat error Multilib version problems found no longer a problem.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team recently helped a customer resolve a commonly seen RedHat error.

What is Multilib version problems found: RedHat error?

The “Multilib version problems found” error is a common occurrence while installing a package. Let’s take a look at how the error message often present itself as seen below:

[root@localhost ~]# yum -y install gcc 
Loaded plugins: fastestmirror 
Loading mirror speeds from cached hostfile 
* base: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
* epel: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
* extras: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
* ius: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
* updates: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Resolving Dependencies 
--> Running transaction check 
... 
--> Finished Dependency Resolution 
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 libgomp which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of libgomp 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 libgomp.otherarch ... this should give you an error message showing the root cause of the problem.
2. You have multiple architectures of libgomp 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 libgomp 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: libgomp-4.8.5-28.el7.i686 != libgomp-4.8.5-28.el7_5.1.x86_64 
Error: Protected multilib versions: nss-softokn-freebl-3.34.0-2.el7.i686 != nss-softokn-freebl-3.36.0-5.el7_5.x86_64 
[root@localhost ]#

Fortunately, our Support Techs have come up with a solution for this particular issue.

How to resolve “Multilib version problems found” error

Although you might come across different solutions for this issue on the internet, our Support Techs advise being wary since it may wind up doing more harm than good.

In fact, this particular solution offered by our Skilled Engineers has been successful for many of our customers. All we have to do to resolve this specific issue is downgrade the version by executing the following command for each Multilib version package:

yum downgrade package_name

For instance:

yum downgrade libgomp
yum downgrade nss-softokn-freebl

In order to ensure the above resolution is successful, we can follow either of these two options:

  1. We can execute the above-mentioned command again to verify.
  2. Another option would be to execute the previous command in order to check for duplicate packages as seen below:
    yum list –showduplicates package_name

    For instance:

    yum list --showduplicates libgomp
    yum list --showduplicates nss-softokn-freebl

    [Need help with a different query? We are available 24/7.]

    Conclusion

    To sum up, the skilled Support Engineers at Bobcares demonstrated how to deal with the Multilib version problems found error.

    PREVENT YOUR SERVER FROM CRASHING!

    Never again lose customers to poor server speed! Let us help you.

    Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

    GET STARTED

I use Centos 7

When I tried to install libstdc++ with yum install libstdc++.i686 I took following massages.

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 libstdc++ which is missing some
            dependency that another package requires. Yum is trying to
            solve this by installing an older version of libstdc++ 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 libstdc++.otherarch ... this should give you an error
            message showing the root cause of the problem.

         2. You have multiple architectures of libstdc++ 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 libstdc++ 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: libstdc++-4.8.5-39.el7.i686 != libstdc++-4.8.5-36.el7_6.2.x86_64

How can I install libstdc++.i686?

asked Apr 6, 2020 at 14:58

Fox's user avatar

FoxFox

611 silver badge8 bronze badges

it helped me

yum update -y libstdc++.x86_64
yum install libstdc++.i686

answered Apr 6, 2020 at 16:18

Fox's user avatar

FoxFox

611 silver badge8 bronze badges

1

do you have try this

yum update —setopt=protected_multilib=false

answered Mar 11, 2021 at 14:00

Acoi Hosting's user avatar

1

Ошибка:  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 xzlibs which is missing some

             dependency that another package requires. Yum is trying to

             solve this by installing an older version of xzlibs 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 xzlibs.otherarch ... this should give you an error

             message showing the root cause of the problem.

          2. You have multiple architectures of xzlibs installed, but

             yum can only see an upgrade for one of those architectures.

             If you dont 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 xzlibs 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).

        Защищённые версии multilib: xzlibs5.2.21.el7.i686 != xzlibs5.1.212alpha.el7.x86_64

Ошибка: Защищённые версии multilib: zlib1.2.717.el7.i686 != zlib1.2.715.el7.x86_64

Ошибка: Защищённые версии multilib: pam1.1.818.el7.i686 != pam1.1.812.el7_1.1.x86_64

Ошибка: Защищённые версии multilib: libsepol2.56.el7.i686 != libsepol2.1.93.el7.x86_64

Business Automation

Business Automation:6.0

Business Automation:6.x

Operations Automation

Operations Automation:5.5

Operations Automation:5.x

Operations Automation:6.0

Operations Automation:6.x

Symptoms

Packages’ update via yum fails with the following error:

> 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 libcurl which is missing some
>             dependency that another package requires. Yum is trying to
>             solve this by installing an older version of libcurl 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 libcurl.otherarch ... this should give you an error
>             message showing the root cause of the problem.
> 
>          2. You have multiple architectures of libcurl installed, but
>             yum can only see an upgrade for one of those arcitectures.
>             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 libcurl 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: libcurl-7.19.7-40.el6_6.3.i686 != libcurl-7.21.3-9.el6.x86_64
>  You could try using --skip-broken to work around the problem
> ** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows:
> libcurl-7.21.3-9.el6.x86_64 is a duplicate with libcurl-7.19.7-36.el6_4.i686

Cause

Scenario 1:

Both x86_64 and i686 versions of libcurl are installed and have different versions:

# rpm -q libcurl
libcurl-7.19.7-36.el6_4.i686
libcurl-7.21.3-9.el6.x86_64

The one available in repositories is i686 but it is still older than 7.21.3-9

# yum -q list available libcurl
Available Packages
libcurl.i686    7.19.7-40.el6_6.3 updates

Scenario 2:

Installed version is different than the one available on the repository:

# rpm -q rrdtool
rrdtool-1.4.4-1.wrl.i386

# yum -q list available rrdtool
Available Packages
rrdtool.i686      1.3.8-7.el6                  base
rrdtool.x86_64    1.3.8-7.el6                  base

Resolution

Check if both x68_64 and i686 versions are used (you can try removing them with rpm -e --test command to see if it shows any dependency errors). If one of those is not used and not needed — remove it.

If both are used and needed then either find and install 7.21.3-9 version of i686 or downgrade x86_64 one to the version 7.19.7-40 or run exclude this package from update list:

# yum --exclude libcurl update

Same approach can be used for other packages too.

Internal content

Hello,

I have the same error in my CENTOS 6.10 kvm with cPanel v76.0.9 since got the last cPanel update.

When I tried to yum update got this error:

<code>
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 libssh2 which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libssh2 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 libssh2.otherarch … this should give you an error
message showing the root cause of the problem.

2. You have multiple architectures of libssh2 installed, but
yum can only see an upgrade for one of those arcitectures.
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 libssh2 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: libssh2-1.4.2-2.el6_7.1.i686 != libssh2-1.8.0-5.0.cf.rhel6.x86_64
</code>

I tried with your solution but without success:
<code>
yum list installed |grep @city
libssh2.x86_64 1.8.0-5.0.cf.rhel6 @city-fan.org

with a lot of packages

rpm -ev —nodeps —justdb libssh2 libssh2-devel
error: package libssh2-devel is not installed

yum install libssh2 libssh2-devel

and said me again:
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……..

</code>

So I tried to see the duplicates packages with
<code>
yum check
Loaded plugins: fastestmirror, protectbase, security, universal-hooks
check all

yum-complete-transaction

0 packages excluded due to repository protections
No unfinished transactions left.

package-cleanup —dupes
Loaded plugins: fastestmirror, protectbase
</code>

not show nothing
<code>
package-cleanup —problems
Loaded plugins: fastestmirror, protectbase
No Problems Found
</code>

Then I proceed to make <code> yum update</code> again but always show me the same alert

Can you help me with this?

Now I am using this command to update my 7.x CentOS:

yum update

show this error:

--> Running transaction check
---> Package kernel.x86_64 0:3.10.0-514.el7 will be erased
--> Finished Dependency Resolution
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 zlib which is missing some
            dependency that another package requires. Yum is trying to
            solve this by installing an older version of zlib 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 zlib.otherarch ... this should give you an error
            message showing the root cause of the problem.

         2. You have multiple architectures of zlib 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 zlib 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: zlib-1.2.7-19.el7_9.i686 != zlib-1.2.7-18.el7.x86_64
Error: Protected multilib versions: systemd-libs-219-78.el7_9.3.i686 != systemd-libs-219-78.el7_9.2.x86_64

I check my system install package:

[root@izbp19pke6x0v6ruecuy1yz ~]# rpm -q zlib-1.2.7-18.el7.x86_64
zlib-1.2.7-18.el7.x86_64

zlib-1.2.7-18.el7.x86_64 is a new version. It tell me to downgrade the zlib version? what should I do? delete the new version of zlib-1.2.7-18.el7.x86_64? why the upgrade use the old version of zlib-1.2.7-18.el7.x86_64? I have deleted the zlib-1.2.7-18.el7.x86_64, but seems make it worse:

[root@izbp19pke6x0v6ruecuy1yz ~]# yum update
Failed to set locale, defaulting to C
Loaded plugins: elrepo, fastestmirror, product-id, search-disabled-repos, subscription-manager

This system is not registered with an entitlement server. You can use subscription-manager to register.

Repository base is listed more than once in the configuration
Repository updates is listed more than once in the configuration
Repository extras is listed more than once in the configuration
Repository centosplus is listed more than once in the configuration
Loading mirror speeds from cached hostfile
 * base: mirrors.163.com
 * centos-sclo-rh: mirrors.163.com
 * centos-sclo-sclo: mirrors.163.com
 * elrepo: hkg.mirror.rackspace.com
 * epel: mirror.sjtu.edu.cn
 * extras: mirrors.163.com
 * remi-safe: mirrors.tuna.tsinghua.edu.cn
 * updates: mirrors.163.com
[elrepo]: 56 kmod packages excluded due to dependency errors
Resolving Dependencies
There are unfinished transactions remaining. You might consider running yum-complete-transaction, or "yum-complete-transaction --cleanup-only" and "yum history redo last", first to finish them. If those don't work you'll have to try removing/installing packages by hand (maybe package-cleanup can help).
The program yum-complete-transaction is found in the yum-utils package.
--> Running transaction check
---> Package systemd-libs.i686 0:219-78.el7_9.2 will be updated
--> Processing Dependency: systemd-libs = 219-78.el7_9.2 for package: systemd-219-78.el7_9.2.x86_64
---> Package systemd-libs.i686 0:219-78.el7_9.3 will be an update
---> Package zlib.i686 0:1.2.7-18.el7 will be updated
--> Processing Dependency: zlib = 1.2.7-18.el7 for package: zlib-devel-1.2.7-18.el7.x86_64
---> Package zlib.i686 0:1.2.7-19.el7_9 will be an update
--> Finished Dependency Resolution
Error: Package: zlib-devel-1.2.7-18.el7.x86_64 (@base)
           Requires: zlib = 1.2.7-18.el7
           Removing: zlib-1.2.7-18.el7.i686 (@base)
               zlib = 1.2.7-18.el7
           Updated By: zlib-1.2.7-19.el7_9.i686 (updates)
               zlib = 1.2.7-19.el7_9
Error: Package: systemd-219-78.el7_9.2.x86_64 (@updates)
           Requires: systemd-libs = 219-78.el7_9.2
           Removing: systemd-libs-219-78.el7_9.2.i686 (@updates)
               systemd-libs = 219-78.el7_9.2
           Updated By: systemd-libs-219-78.el7_9.3.i686 (updates)
               systemd-libs = 219-78.el7_9.3
           Available: systemd-libs-219-78.el7.i686 (base)
               systemd-libs = 219-78.el7
 You could try using --skip-broken to work around the problem
** Found 29 pre-existing rpmdb problem(s), 'yum check' output follows:
centos-release-7-9.2009.1.el7.centos.x86_64 is a duplicate with centos-release-7-9.2009.0.el7.centos.x86_64
dnf-data-4.0.9.2-2.el7_9.noarch is a duplicate with dnf-data-4.0.9.2-1.el7_6.noarch
1:grub2-common-2.02-0.87.el7.centos.6.noarch is a duplicate with 1:grub2-common-2.02-0.86.el7.centos.noarch
1:grub2-pc-2.02-0.87.el7.centos.6.x86_64 is a duplicate with 1:grub2-pc-2.02-0.86.el7.centos.x86_64
1:grub2-pc-modules-2.02-0.87.el7.centos.6.noarch is a duplicate with 1:grub2-pc-modules-2.02-0.86.el7.centos.noarch
1:grub2-tools-2.02-0.87.el7.centos.6.x86_64 is a duplicate with 1:grub2-tools-2.02-0.86.el7.centos.x86_64
1:grub2-tools-extra-2.02-0.87.el7.centos.6.x86_64 is a duplicate with 1:grub2-tools-extra-2.02-0.86.el7.centos.x86_64
1:grub2-tools-minimal-2.02-0.87.el7.centos.6.x86_64 is a duplicate with 1:grub2-tools-minimal-2.02-0.86.el7.centos.x86_64
libblkid-2.23.2-65.el7_9.1.x86_64 is a duplicate with libblkid-2.23.2-65.el7.x86_64
libmount-2.23.2-65.el7_9.1.x86_64 is a duplicate with libmount-2.23.2-65.el7.x86_64
libsmartcols-2.23.2-65.el7_9.1.x86_64 is a duplicate with libsmartcols-2.23.2-65.el7.x86_64
libuuid-2.23.2-65.el7_9.1.x86_64 is a duplicate with libuuid-2.23.2-65.el7.x86_64
linux-firmware-20200421-80.git78c0348.el7_9.noarch is a duplicate with linux-firmware-20200421-79.git78c0348.el7.noarch
1:openssl-libs-1.0.2k-21.el7_9.x86_64 is a duplicate with 1:openssl-libs-1.0.2k-19.el7.x86_64
4:perl-5.16.3-299.el7_9.x86_64 is a duplicate with 4:perl-5.16.3-297.el7.x86_64
4:perl-libs-5.16.3-299.el7_9.x86_64 is a duplicate with 4:perl-libs-5.16.3-297.el7.x86_64
4:perl-macros-5.16.3-299.el7_9.x86_64 is a duplicate with 4:perl-macros-5.16.3-297.el7.x86_64
python-requests-2.6.0-10.el7.noarch has missing requires of python-urllib3 >= ('0', '1.10.2', '1')
python2-dnf-4.0.9.2-2.el7_9.noarch is a duplicate with python2-dnf-4.0.9.2-1.el7_6.noarch
systemd-219-78.el7_9.3.x86_64 is a duplicate with systemd-219-78.el7_9.2.x86_64
systemd-libs-219-78.el7_9.3.x86_64 is a duplicate with systemd-libs-219-78.el7_9.2.i686
systemd-sysv-219-78.el7_9.3.x86_64 is a duplicate with systemd-sysv-219-78.el7_9.2.x86_64
tzdata-2021a-1.el7.noarch is a duplicate with tzdata-2020d-2.el7.noarch
util-linux-2.23.2-65.el7_9.1.x86_64 is a duplicate with util-linux-2.23.2-65.el7.x86_64
2:vim-common-7.4.629-8.el7_9.x86_64 is a duplicate with 2:vim-common-7.4.629-7.el7.x86_64
2:vim-filesystem-7.4.629-8.el7_9.x86_64 is a duplicate with 2:vim-filesystem-7.4.629-7.el7.x86_64
2:vim-minimal-7.4.629-8.el7_9.x86_64 is a duplicate with 2:vim-minimal-7.4.629-7.el7.x86_64
zlib-1.2.7-19.el7_9.x86_64 is a duplicate with zlib-1.2.7-18.el7.i686
zlib-devel-1.2.7-19.el7_9.x86_64 is a duplicate with zlib-devel-1.2.7-18.el7.x86_64

Introduction

The error message as in the title of the article is actually exist upon installing a package. The following are the exact output of the error message on installing a package with the name of ‘gcc’ :

[root@localhost ~]# yum -y install gcc
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 * epel: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 * extras: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 * ius: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 * updates: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Resolving Dependencies
--> Running transaction check
...
--> Finished Dependency Resolution
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 libgomp which is missing some
            dependency that another package requires. Yum is trying to
            solve this by installing an older version of libgomp 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 libgomp.otherarch ... this should give you an error
            message showing the root cause of the problem.
       
         2. You have multiple architectures of libgomp 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 libgomp 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: libgomp-4.8.5-28.el7.i686 != libgomp-4.8.5-28.el7_5.1.x86_64
Error: Protected multilib versions: nss-softokn-freebl-3.34.0-2.el7.i686 != nss-softokn-freebl-3.36.0-5.el7_5.x86_64
[root@localhost ]#

Avoiding a possible destructive solution

Upon searching for the solution using google, there is a temporary to solve the problem. It is not a solution after all because it will create another bigger problem. DO NOT DO THE FOLLOWING COMMAND, TAKE IT AS YOUR OWN RISK. THE FOLLOWING IS THE EXECUTION OF THE COMMAND WHICH IS NOT HELPING FOR SOLVING THE PROBLEM :

[root@localhost ~]# rpm --erase --nodeps libgomp
[root@localhost ~]# rpm --erase --nodeps nss-softokn-freebl
[root@localhost ~]# 

The above solution JUST MAKE THE PROBLEM WORSE. The possible best solution is to just downgrade the version of the package so there will be no duplicate version. Sadly, there is no chance for me to prove that the following solution works. It happens because I have already executed the above command and it damaged the system.

Downgrade the version by executing the following command for every multilib version’s package :

Pattern : yum downgrade package_name

For an example :

yum downgrade libgomp
yum downgrade nss-softokn-freebl

Finally, in order to check the solution has come to a correct result, do the following :

1. Just re-execute the above command. The command is installing a package with the name of ‘gcc’. So, the command is : ‘yum -y install gcc’.

2. Another method, just execute the following command to check for duplicate package :

Pattern : yum list –showduplicates package_name

For an example :

yum list --showduplicates libgomp
yum list --showduplicates nss-softokn-freebl

pjc123

Posts: 80
Joined: 2010/08/17 16:59:11
Contact:

SOLVED: YUM Fails With Multilib version problems found

So, I tried doing a YUM update today and it will not run because of the following error; it worked fine for many months. I was able to upgrade all the other packages by doing a dnf update and bypassing YUM. How do I fix this error?:

Resolving Dependencies
—> Running transaction check
—> Package libgpg-error.x86_64 0:1.12-3.el7 will be updated
—> Package libgpg-error.x86_64 0:1.29-1.el7.centos will be an update
—> Finished Dependency Resolution
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 libgpg-error which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libgpg-error 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 libgpg-error.otherarch … this should give you an error
message showing the root cause of the problem.

2. You have multiple architectures of libgpg-error 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 libgpg-error 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: libgpg-error-1.29-1.el7.centos.x86_64 != libgpg-error-1.12-3.el7.i686

Last edited by pjc123 on 2018/05/20 11:51:47, edited 1 time in total.


User avatar

TrevorH

Site Admin
Posts: 32527
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: YUM Fails With Multilib version problems found

Post

by TrevorH » 2018/05/19 21:13:04

We don’t ship a libgpg-error-1.29-1.el7.centos.x86_64. Can you post all of the output from

yum list libgpg-error —noplugins —showdupli

right from the command prompt where you enter the command, all the way until the command prompt returns.


pjc123

Posts: 80
Joined: 2010/08/17 16:59:11
Contact:

Re: YUM Fails With Multilib version problems found

Post

by pjc123 » 2018/05/19 21:57:28

Thanks for the reply. You are on the right track, because my KeepassXC program stopped working at the same time, and it shows up in the yum list:

$ yum list libgpg-error —noplugins —showdupli
google-chrome 3/3
Installed Packages
libgpg-error.i686 1.12-3.el7 @base
libgpg-error.x86_64 1.12-3.el7 @anaconda
Available Packages
libgpg-error.i686 1.12-3.el7 base
libgpg-error.x86_64 1.12-3.el7 base
libgpg-error.x86_64 1.13-1.el7.centos bugzy-keepassxc
libgpg-error.x86_64 1.29-1.el7.centos bugzy-keepassxc


User avatar

TrevorH

Site Admin
Posts: 32527
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: YUM Fails With Multilib version problems found

Post

by TrevorH » 2018/05/19 22:10:58

So it’s coming from this «bugzy-keepassxc» repo that you have installed and it looks like it’s been overwriting the CentOS copy for a while because there’s more than one version in that list. We don’t recommend any repos that overwrite/replace packages from the CentOS repos — in fact it’s one of the things that gets repos moved into the «look out for this» category in the wiki article about third party repos.

You might want to look at the various packages in EPEL that look similar and see if any of those would fulfil your needs.

Code: Select all

# yum list keepass*
Loaded plugins: priorities
694 packages excluded due to repository priority protections
Available Packages
keepass.x86_64                                             2.34-1.el7                                            epel
keepass-doc.noarch                                         2.34-1.el7                                            epel
keepassx.x86_64                                            0.4.4-1.el7                                           epel
keepassx2.x86_64                                           2.0.3-2.el7                                           epel


pjc123

Posts: 80
Joined: 2010/08/17 16:59:11
Contact:

Re: YUM Fails With Multilib version problems found

Post

by pjc123 » 2018/05/19 22:26:44

A little background. Keepassxc is a Password Management program and is a fork of Keepass and Keepassx; it is better maintained than those other programs, with bug fixes and new features. I also use it with Linux Mint, Windows 10 and Android, but no issues with any of them. Anyway, I think I can use those other programs instead, to open the password database file. I will check and see if that is true, and that it will not corrupt the database file. Not sure those other programs will have the same issue replacing the libgpg-error file though? That said, sorry for the newbie question, but what do I need to delete, add, etc. to get Centos back to its original state with the libgpg-error files, as the OS being correct is the important thing.


User avatar

TrevorH

Site Admin
Posts: 32527
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: YUM Fails With Multilib version problems found

Post

by TrevorH » 2018/05/19 22:40:49

EPEL has a policy of not replacing packages from the base repos so anything from there should be safe… mostly. There is some movement of packages between EPEL and RHEL and back again so sometimes there are copies in EPEL that are duplicates of the ones in base as they will have just been added to RHEL (or are about to be removed from it). One example is the awscli package which was added to RHEL 7.5 but still exists in EPEL as it hasn’t been removed yet.

I would install EPEL if you haven’t got it already — use yum —enablerepo=extras install epel-release — and then yum install keychecker . Run keychecker and it will produce a long list of all your installed packages, grouped by the signing GPG key so you can see what comes from what repo. If they’re signed (which I assume that they will be given that the package you’re after is one for the security conscious) then there will be a section for that repo and the packages listed there will be the ones that you would need to either remove or downgrade using yum downgrade $package. If the packages are not signed then they will be in the «unsigned» section at the end of the report.


pjc123

Posts: 80
Joined: 2010/08/17 16:59:11
Contact:

Re: YUM Fails With Multilib version problems found

Post

by pjc123 » 2018/05/20 01:08:36

Thanks for all the help. I am going to remove KeepassXC and the repo, delete all instances of libgpg-error, reinstall the Centos versions of libgpg-error, and look into the feasibility of using the other Keepass programs.


User avatar

TrevorH

Site Admin
Posts: 32527
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: YUM Fails With Multilib version problems found

Post

by TrevorH » 2018/05/20 01:16:14

You won’t be able to yum remove libgpg-error, it’ll want to take systemd and yum with it and yum will refuse to let you do that. Use `yum downgrade libgpg-error` to go backwards after disabling or removing the repo and it will go back to the distro copy.



pjc123

Posts: 80
Joined: 2010/08/17 16:59:11
Contact:

Re: YUM Fails With Multilib version problems found

Post

by pjc123 » 2018/05/20 11:50:27

SOLVED: Thanks to TrevorH, YUM is working again. Also, I am up and running with KeepassXC again, because it was made to my attention that there is an AppImage version of the KeepassXC program that is a standalone program and it does not touch any operating system files.


  • #1

Hello

Cent OS 6.5
Plesk 12.5.30

I can not update plesk

[[email protected] ~]# yum clean all
Loaded plugins: fastestmirror
Cleaning repos: atomic base epel extras openvz-kernel-rhel6 openvz-utils plesk-php-5.3 plesk-php-5.4 plesk-php-5.5 plesk-php-5.6 updates vz-base
: vz-updates webtatic
Cleaning up Everything
Cleaning up list of fastest mirrors
[[email protected] ~]# yum update -y
Loaded plugins: fastestmirror
Setting up Update Process
Determining fastest mirrors
epel/metalink | 22 kB 00:00
* atomic: www4.atomicorp.com
* base: mirror.switch.ch
* epel: mirror.switch.ch
* extras: mirror.switch.ch
* openvz-kernel-rhel6: mirror.23media.de
* openvz-utils: mirror.23media.de
* updates: mirror.switch.ch
* webtatic: uk.repo.webtatic.com
atomic | 3.4 kB 00:00
atomic/primary_db | 1.1 MB 00:00
base | 3.7 kB 00:00
base/primary_db | 4.7 MB 00:00
epel | 4.3 kB 00:00
epel/primary_db | 5.8 MB 00:00
extras | 3.4 kB 00:00
extras/primary_db | 37 kB 00:00
openvz-kernel-rhel6 | 2.8 kB 00:00
openvz-kernel-rhel6/primary_db | 9.1 kB 00:00
openvz-utils | 2.5 kB 00:00
openvz-utils/primary_db | 27 kB 00:00
plesk-php-5.3 | 2.9 kB 00:00
plesk-php-5.3/primary_db | 14 kB 00:00
plesk-php-5.4 | 2.9 kB 00:00
plesk-php-5.4/primary_db | 14 kB 00:00
plesk-php-5.5 | 2.9 kB 00:00
plesk-php-5.5/primary_db | 14 kB 00:00
plesk-php-5.6 | 2.9 kB 00:00
plesk-php-5.6/primary_db | 14 kB 00:00
updates | 3.4 kB 00:00
updates/primary_db | 1.4 MB 00:00
vz-base | 951 B 00:00
vz-base/primary | 1.3 kB 00:00
vz-base 3/3
vz-updates | 951 B 00:00
vz-updates/primary | 2.2 kB 00:00
vz-updates 8/8
webtatic | 3.6 kB 00:00
webtatic/primary_db | 169 kB 00:00
Resolving Dependencies
There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them.
The program yum-complete-transaction is found in the yum-utils package.
—> Running transaction check
—> Package nss-softokn-freebl.i686 0:3.14.3-23.el6_7 will be updated
—> Package nss-softokn-freebl.i686 0:3.14.3-23.3.el6_8 will be an update
—> Package tar.x86_64 2:1.23-14.el6 will be updated
—> Package tar.x86_64 2:1.23-15.el6_8 will be an update
—> Finished Dependency Resolution
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 arcitectures.
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.14.3-23.3.el6_8.i686 != nss-softokn-freebl-3.14.3-23.el6_7.x86_64

How can i fix this?

  • #3

Thank you. But yum update do not work

Code:

Last login: Mon Aug 29 12:53:06 2016 from 31.10.131.203
[[email protected] ~]# yum update
Loaded plugins: fastestmirror
Setting up Update Process
Loading mirror speeds from cached hostfile
* atomic: www4.atomicorp.com
* base: mirror.switch.ch
* epel: mirror.switch.ch
* extras: mirror.switch.ch
* openvz-kernel-rhel6: mirror.23media.de
* openvz-utils: mirror.23media.de
* updates: mirror.switch.ch
* webtatic: uk.repo.webtatic.com
Resolving Dependencies
There are unfinished transactions remaining. You might consider running yum-comp                                                                                                                                                             lete-transaction first to finish them.
The program yum-complete-transaction is found in the yum-utils package.

So how can I complete these transactions?

Понравилась статья? Поделить с друзьями:
  • Error multidimensional array must have bounds for all dimensions except the first
  • Error mugen character
  • Error msg установка драйвера ошибка установки msg error monetreport
  • Error msg unable to process command password is set but no password file is provided
  • Error msg bcu return value real 10 translated 10