Skip to main content

libsss_idmap dependancy failure

MartinC
Is anyone else getting rpmup failures on libsss_idmap? I have a few servers failing to update and it looks like it's trying to install a 32 bit package which is causing a conflict: ---> Package libsss_idmap.x86_64 0:1.16.5-10.el7_9.10 will be updated --> Processing Dependency: libsss_idmap = 1.16.5-10.el7_9.10 for package: sssd-client-1.16.5-10.el7_9.10.x86_64 ---> Package libsss_idmap.x86_64 0:1.16.5-10.el7_9.11 will be an update ---> Package libsss_nss_idmap.x86_64 0:1.16.5-10.el7_9.10 will be updated --> Processing Dependency: libsss_nss_idmap = 1.16.5-10.el7_9.10 for package: sssd-client-1.16.5-10.el7_9.10.x86_64 ---> Package libsss_nss_idmap.x86_64 0:1.16.5-10.el7_9.11 will be an update ---> Package mdadm.x86_64 0:4.1-7.el7_9 will be updated ---> Package mdadm.x86_64 0:4.1-8.el7_9 will be an update --> Running transaction check ---> Package libsss_idmap.i686 0:1.16.5-10.el7_9.10 will be installed --> Processing Dependency: libdl.so.2 for package: libsss_idmap-1.16.5-10.el7_9.10.i686 --> Processing Dependency: libc.so.6(GLIBC_2.4) for package: libsss_idmap-1.16.5-10.el7_9.10.i686 ---> Package libsss_idmap.x86_64 0:1.16.5-10.el7_9.10 will be updated ---> Package libsss_nss_idmap.i686 0:1.16.5-10.el7_9.10 will be installed ---> Package libsss_nss_idmap.x86_64 0:1.16.5-10.el7_9.10 will be updated --> Running transaction check ---> Package glibc.i686 0:2.17-325.el7_9 will be installed --> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-325.el7_9.i686 --> Processing Dependency: libfreebl3.so for package: glibc-2.17-325.el7_9.i686 --> Running transaction check ---> Package nss-softokn-freebl.i686 0:3.67.0-3.el7_9 will be installed --> 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 libsss_nss_idmap which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of libsss_nss_idmap 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 libsss_nss_idmap.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of libsss_nss_idmap 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 libsss_nss_idmap 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: libsss_nss_idmap-1.16.5-10.el7_9.11.x86_64 != libsss_nss_idmap-1.16.5-10.el7_9.10.i686 Error: Protected multilib versions: libsss_idmap-1.16.5-10.el7_9.11.x86_64 != libsss_idmap-1.16.5-10.el7_9.10.i686 I've tried a yum clean all, but still getting the error.

Comments

4 comments

Date Votes
  • cPanelAnthony
    Hello! The error message suggests the following. [QUOTE] --exclude libsss_nss_idmap.otherarch ... this should give you an error message showing the root cause of the problem.
    Maybe you could try this to get the "root cause" error message?
    0
  • vytas
    I got similar thing... [CODE=bash]bash-4.2# yum update --exclude libsss_idmap.otherarch Loaded plugins: fastestmirror, langpacks, universal-hooks Loading mirror speeds from cached hostfile * EA4: 185.15.22.168 * cpanel-addons-production-feed: 185.15.22.168 * cpanel-plugins: 185.15.22.168 Resolving Dependencies --> Running transaction check ---> Package bash.x86_64 0:4.2.46-34.el7 will be updated ---> Package bash.x86_64 0:4.2.46-35.el7_9 will be an update ---> Package bind.x86_64 32:9.11.4-26.P2.el7_9.7 will be updated ---> Package bind.x86_64 32:9.11.4-26.P2.el7_9.8 will be an update ---> Package bind-devel.x86_64 32:9.11.4-26.P2.el7_9.7 will be updated ---> Package bind-devel.x86_64 32:9.11.4-26.P2.el7_9.8 will be an update ---> Package bind-export-libs.x86_64 32:9.11.4-26.P2.el7_9.7 will be updated ---> Package bind-export-libs.x86_64 32:9.11.4-26.P2.el7_9.8 will be an update ---> Package bind-libs.x86_64 32:9.11.4-26.P2.el7_9.7 will be updated ---> Package bind-libs.x86_64 32:9.11.4-26.P2.el7_9.8 will be an update ---> Package bind-libs-lite.x86_64 32:9.11.4-26.P2.el7_9.7 will be updated ---> Package bind-libs-lite.x86_64 32:9.11.4-26.P2.el7_9.8 will be an update ---> Package bind-license.noarch 32:9.11.4-26.P2.el7_9.7 will be updated ---> Package bind-license.noarch 32:9.11.4-26.P2.el7_9.8 will be an update ---> Package bind-lite-devel.x86_64 32:9.11.4-26.P2.el7_9.7 will be updated ---> Package bind-lite-devel.x86_64 32:9.11.4-26.P2.el7_9.8 will be an update ---> Package bind-utils.x86_64 32:9.11.4-26.P2.el7_9.7 will be updated ---> Package bind-utils.x86_64 32:9.11.4-26.P2.el7_9.8 will be an update ---> Package kbd.x86_64 0:1.15.5-15.el7 will be updated ---> Package kbd.x86_64 0:1.15.5-16.el7_9 will be an update ---> Package kbd-legacy.noarch 0:1.15.5-15.el7 will be updated ---> Package kbd-legacy.noarch 0:1.15.5-16.el7_9 will be an update ---> Package kbd-misc.noarch 0:1.15.5-15.el7 will be updated ---> Package kbd-misc.noarch 0:1.15.5-16.el7_9 will be an update ---> Package kernel.x86_64 0:3.10.0-1160.49.1.el7 will be installed ---> Package kernel-headers.x86_64 0:3.10.0-1160.45.1.el7 will be updated ---> Package kernel-headers.x86_64 0:3.10.0-1160.49.1.el7 will be an update ---> Package kernel-tools.x86_64 0:3.10.0-1160.45.1.el7 will be updated ---> Package kernel-tools.x86_64 0:3.10.0-1160.49.1.el7 will be an update ---> Package kernel-tools-libs.x86_64 0:3.10.0-1160.45.1.el7 will be updated ---> Package kernel-tools-libs.x86_64 0:3.10.0-1160.49.1.el7 will be an update ---> Package libsss_idmap.x86_64 0:1.16.5-10.el7_9.10 will be updated --> Processing Dependency: libsss_idmap = 1.16.5-10.el7_9.10 for package: sssd-client-1.16.5-10.el7_9.10.x86_64 ---> Package libsss_idmap.x86_64 0:1.16.5-10.el7_9.11 will be an update ---> Package libsss_nss_idmap.x86_64 0:1.16.5-10.el7_9.10 will be updated --> Processing Dependency: libsss_nss_idmap = 1.16.5-10.el7_9.10 for package: sssd-client-1.16.5-10.el7_9.10.x86_64 ---> Package libsss_nss_idmap.x86_64 0:1.16.5-10.el7_9.11 will be an update ---> Package mdadm.x86_64 0:4.1-7.el7_9 will be updated ---> Package mdadm.x86_64 0:4.1-8.el7_9 will be an update --> Running transaction check ---> Package libsss_idmap.i686 0:1.16.5-10.el7_9.10 will be installed --> Processing Dependency: libdl.so.2 for package: libsss_idmap-1.16.5-10.el7_9.10.i686 --> Processing Dependency: libc.so.6(GLIBC_2.4) for package: libsss_idmap-1.16.5-10.el7_9.10.i686 ---> Package libsss_idmap.x86_64 0:1.16.5-10.el7_9.10 will be updated ---> Package libsss_nss_idmap.i686 0:1.16.5-10.el7_9.10 will be installed ---> Package libsss_nss_idmap.x86_64 0:1.16.5-10.el7_9.10 will be updated --> Running transaction check ---> Package glibc.i686 0:2.17-325.el7_9 will be installed --> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-325.el7_9.i686 --> Processing Dependency: libfreebl3.so for package: glibc-2.17-325.el7_9.i686 --> Running transaction check ---> Package nss-softokn-freebl.i686 0:3.67.0-3.el7_9 will be installed --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:3.10.0-1160.6.1.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 libsss_idmap which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of libsss_idmap 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 libsss_idmap.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of libsss_idmap 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 libsss_idmap 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: libsss_idmap-1.16.5-10.el7_9.11.x86_64 != libsss_idmap-1.16.5-10.el7_9.10.i686 Error: Protected multilib versions: libsss_nss_idmap-1.16.5-10.el7_9.11.x86_64 != libsss_nss_idmap-1.16.5-10.el7_9.10.i686
    0
  • vytas
    I think I got a solution. My cPanel installation is on Azure CentOS VM which was using OpenLogic mirrors. So after changing to default CentOS mirrors all worked fine. Just try it on your own risk :) All I did was: [CODE=bash]nano /etc/yum.repos.d/CentOS-Base.repo
    Uncomment all lines starting with "mirrorlist" and commented starting with "beseurl". My CentOS-Base.repo file looked like this: [CODE=INI]# CentOS-Base.repo # # The mirror system uses the connecting IP address of the client and the # update status of each mirror to pick mirrors that are updated to and # geographically close to the client. You should use this for CentOS updates # unless you are manually picking other mirrors. # # If the mirrorlist= does not work for you, as a fall back you can try the # remarked out baseurl= line instead. # # [base] name=CentOS-$releasever - Base mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra #baseurl=http://olcentgbl.trafficmanager.net/centos/$releasever/os/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 #released updates [updates] name=CentOS-$releasever - Updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates&infra=$infra #baseurl=http://olcentgbl.trafficmanager.net/centos/$releasever/updates/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 #additional packages that may be useful [extras] name=CentOS-$releasever - Extras mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra #baseurl=http://olcentgbl.trafficmanager.net/centos/$releasever/extras/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 #additional packages that extend functionality of existing packages [centosplus] name=CentOS-$releasever - Plus mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus&infra=$infra #baseurl=http://olcentgbl.trafficmanager.net/centos/$releasever/centosplus/$basearch/ gpgcheck=1 enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    then run [CODE=bash]yum clean all yum update
    0
  • MartinC
    Yep, I ended up raising a ticket and it was indeed the trafficmanager.net urls that were causing the problem. Switching to the default CPanel urls has fixed the problem for me: [CODE=ini][base] name=CentOS-$releasever - Base #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra baseurl=http://centos2.cpanel.net/centos/$releasever/os/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 #released updates [updates] name=CentOS-$releasever - Updates #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates&infra=$infra baseurl=http://centos2.cpanel.net/centos/$releasever/updates/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 #additional packages that may be useful [extras] name=CentOS-$releasever - Extras #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra baseurl=http://centos2.cpanel.net/centos/$releasever/extras/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 #additional packages that extend functionality of existing packages [centosplus] name=CentOS-$releasever - Plus #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus&infra=$infra baseurl=http://centos2.cpanel.net/centos/$releasever/centosplus/$basearch/ gpgcheck=1 enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    Thanks Vytas, and I think you are right about it being the Azure VM template that set these urls. And thanks to Ryland in Centos support too.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post