I am running yum update or yum update --skip-broken on RHEL6. I am getting the following error, can you provide some insight as to what I should do?

--> Finished Dependency Resolution Error: sssd conflicts with selinux-policy-3.7.19-93.el6.noarch Error: python-devel conflicts with python-2.6.6-20.el6.x86_64 Error: initscripts conflicts with lvm2-2.02.83-3.el6.x86_64 You could try using --skip-broken to work around the problem

sssd-1.9.2-82.4.el6_4.x86_64 from rhel-x86_64-server-6
sssd-client-1.9.2-82.4.el6_4.x86_64 from rhel-x86_64-server-6

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

2. You have multiple architectures of python-rhsm 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 python-rhsm 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).

This sounds like you have incompatible repos installed
can you post the output of this
that outputs the software repos that are installed and if they are ON or OFF

OR
You installed something NOT using yum but using "rpm" to install a rpm package


RHEL6.4 just came out so
there will not be too many updates right now after the first one , if this is a new install .

also you can try rebuilding the yum and rpm database
This is the first thing to try in fixing a yum issue

sometimes the first command fails
if it dose reverse the order

[root@ ~]# yum repolist all
Loaded plugins: product-id, refresh-packagekit, rhnplugin, subscription-manager
This system is registered to Red Hat Subscription Management, but is not receiving updates. You can use subscription-manager to assign subscriptions.
This system is receiving updates from RHN Classic or RHN Satellite.
repo id repo name status
InstallMedia Red Hat Enterprise Linux 6.1 disabled
adobe-linux-i386 Adobe Systems Incorporated enabled: 17
rhel-source Red Hat Enterprise Linux 6Server - x86_64 disabled
rhel-source-beta Red Hat Enterprise Linux 6Server Beta - x disabled
rhel-x86_64-server-6 Red Hat Enterprise Linux Server (v. 6 for enabled: 10,238
rhel-x86_64-server-optional-6 RHEL Server Optional (v. 6 64-bit x86_64) enabled: 6,036
rhel-x86_64-server-supplementary-6 RHEL Server Supplementary (v. 6 64-bit x8 enabled: 399
rhn-tools-rhel-x86_64-server-6 RHN Tools for RHEL (v. 6 for 64-bit x86_6 enabled: 9

I will try the next suggestion you posted and reply. thank you for your help.

I did the following
1)
su -
yum clean all
rpm --rebuilddb
yum update --skip-broken <------!!!


2)
it looks like it is getting hung up on :
--> Processing Conflict: initscripts-9.03.38-1.el6_4.1.x86_64 conflicts lvm2 < 2.02.97-2
--> Processing Conflict: sssd-1.9.2-82.4.el6_4.x86_64 conflicts selinux-policy < 3.7.19-160
--> Processing Conflict: python-devel-2.6.6-36.el6.x86_64 conflicts python < 2.6.6-36.el6

3)
Here is the output from yum update --skip-broken

--> Finished Dependency Resolution

Packages skipped because of dependency problems:
initscripts-9.03.38-1.el6_4.1.x86_64 from rhel-x86_64-server-6
libipa_hbac-1.9.2-82.4.el6_4.x86_64 from rhel-x86_64-server-6
libipa_hbac-python-1.9.2-82.4.el6_4.x86_64 from rhel-x86_64-server-6
libsss_idmap-1.9.2-82.4.el6_4.x86_64 from rhel-x86_64-server-6
python-devel-2.6.6-36.el6.x86_64 from rhel-x86_64-server-6
sssd-1.9.2-82.4.el6_4.x86_64 from rhel-x86_64-server-6
sssd-client-1.9.2-82.4.el6_4.x86_64 from rhel-x86_64-server-6
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 python-rhsm which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of python-rhsm 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 python-rhsm.otherarch ... this should give you an error
message showing the root cause of the problem.

2. You have multiple architectures of python-rhsm 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 python-rhsm 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: python-rhsm-0.99.12-1.el6.noarch != python-rhsm-1.1.8-1.el6.x86_64


--> Processing Conflict: initscripts-9.03.38-1.el6_4.1.x86_64 conflicts lvm2 < 2.02.97-2
--> Processing Conflict: sssd-1.9.2-82.4.el6_4.x86_64 conflicts selinux-policy < 3.7.19-160
--> Processing Conflict: python-devel-2.6.6-36.el6.x86_64 conflicts python < 2.6.6-36.el6
--> Finished Dependency Resolution
Error: initscripts conflicts with lvm2-2.02.83-3.el6.x86_64
Error: python-devel conflicts with python-2.6.6-20.el6.x86_64
Error: sssd conflicts with selinux-policy-3.7.19-93.el6.noarch
You could try using --skip-broken to work around the problem


I would like to know how to handle these conflicts.

this is a you 32 bit VS. 64 bit conundrum

the 32 bit is in conflict with the 64 bit

i would start with uninstalling the 32 bit python

the "yum remove python-32bit" might want to remove half of the operating system .
at least the 32 bit compatibility part

unfortunately with this type of software repo mismatch it is basically a logic guessing game


one best suited for the paid red hat support you have
you might want to call them

you are correct. There are also a couple redhat bugs posts in connection with this. One of them being https://bugzilla.redhat.com/show_bug.cgi?id=735768

after doing what you suggested and editing /boot/grub/grub.conf(remove rhgb and quiet) and disabling selinux in /etc/sysconfig/selinux, we got the updates applied and the system booted.

[root@www-sj1-12 ~]# yum update --skip-broken
Loaded plugins: aliases, changelog, downloadonly, fastestmirror, filter-data, keys, kmod, list-data, protectbase, security, tmprepo, verify, versionlock
Determining fastest mirrors
* epel: mirror.sfo12.us.leaseweb.net
epel | 3.7 kB 00:00
epel/primary_db | 3.4 MB 00:00
nodesource | 2.5 kB 00:00
nodesource/primary_db | 21 kB 00:00
Skipping filters plugin, no data
0 packages excluded due to repository protections
Skipping security plugin, no data
Reading version lock configuration
Setting up Update Process
Resolving Dependencies
Skipping filters plugin, no data
Skipping security plugin, no data
--> Running transaction check
---> Package facter.x86_64 0:1.6.18-3.el5 set to be updated
--> Processing Dependency: virt-what for package: facter
--> Finished Dependency Resolution
facter-1.6.18-3.el5.x86_64 from epel has depsolving problems
--> Missing Dependency: virt-what is needed by package facter-1.6.18-3.el5.x86_64 (epel)

Packages skipped because of dependency problems:
facter-1.6.18-3.el5.x86_64 from epel

aknal123

is there a question here????

this is a old 2+ year old thread that you resurrected from the dead

plus this thread is about the two year OLD RHEL6.3

your output has you on rhel5
the LEGACY "hardware / software" operating system


please start a NEW thread
and READ
" how to post a question"
http://www.linuxquestions.org/linux/...Ask_a_Question