Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
i have RHEL 6.3

[root@RHEL6 yum.repos.d]# uname -a
Linux RHEL6.3-64-BuildMac 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012     x86_64 x86_64 x86_64 GNU/Linux

My /etc/yum.conf looks like  

The contents of my /etc.yum.repo.d/rhel.repo looks like
name=my rhel repo  

But my yum update fails with the following error

[root@RHEL6 yum.repos.d]# yum update  
Loaded plugins: product-id, security, subscription-manager
Updating certificate-based repositories.
Unable to read consumer identity
Setting up Update Process
No Packages marked for Update

please could somebody help

share|improve this question

migrated from Oct 1 '12 at 16:18

This question came from our site for professional and enthusiast programmers.

Disable subscription manager and try

Change enable=0 in /etc/yum/pluginconf.d/product-id.conf and /etc/yum/pluginconf.d/subscription-manager.conf



and then clean cache

rm -rfv /var/cache/yum/*

yum clean all

share|improve this answer
Mine was hanging at "updating certificate-based repositories", and this solution worked for me, thanks. Note that I did not have an active RHEL subscription on that machine. – Liam Apr 14 '14 at 10:17

This may be of help. I haven't had this error myself, though, so I couldn't test.

share|improve this answer
sorry it does not help!! – user1670818 Oct 1 '12 at 12:44

RHEL requires that you identify yourself as a legitimate customer for updates, and the error message you posted seems to say that failed.

share|improve this answer

To fix the "Unable to read consumer identity" warning:

$ vi /etc/yum/pluginconf.d/subscription-manager.conf

Then change enabled to 0 so the file looks like this:


Then your "Unable to read consumer identity" warning will go away. Also, your update probably was not failing, there were probably just no packages to update at the time. Leaving it with the warning is fine too, it has no functional impact.

share|improve this answer

You must log in to answer this question.