RHN yum command: Unable to read consumer identity Warning and Solution

I am using yum update command with RHN to upgrade packages installed on my server, but getting the following warning on screen :

yum update -y
Loaded plugins: product-id, protectbase, rhnplugin, security, subscription manager:
Updating certificate-based repositories.
Unable to read consumer identity
0 packages excluded due to repository protections
Setting up Update Process
Resolving Dependencies
--> Running transaction check

How do I get rid of this warning /error under RHEL 6 server?

You need to edit the following files

[a] /etc/yum/pluginconf.d/subscription-manager.conf

[b] /etc/yum/pluginconf.d/product-id.conf

Use a text editor such as vi:
# vi /etc/yum/pluginconf.d/product-id.conf /etc/yum/pluginconf.d/subscription-manager.conf
Set enabled to 0 as follows in both files:


Save and close the file. Finally, type the following command to clean cache:

rm -rfv /var/cache/yum/*
yum clean all

You can now install or update the system:
# yum install packageNameHere
# yum -y update


As per RHEL KB # 165803 root cause for this error was:

When RHN Classic or RHN Satellite is used for updating the system, subscription-manager should be disabled.

Posted by: SXI ADMIN

The author is the creator of nixCraft and a seasoned sysadmin, DevOps engineer, and a trainer for the Linux operating system/Unix shell scripting. Get the latest tutorials on SysAdmin, Linux/Unix and open source topics via RSS/XML feed or weekly email newsletter.


Start your Bitcoin Exchange with our Software

Start your Bitcoin Exchange with our Software Setup your white label bitcoin exchange right away. Or create your own cryptocurrency using...

How to KVM, QEMU start or stop virtual machine from command line (CLI)

KVM or Kernel Based Virtual Machine is a popular virtualization technology. It allows you to run virtual guest machines over a host machine. To start...

How to Docker backup Saving and restoring your volumes

Running a Docker volume backup First, we spin up a temporary container, and we mount the backup folder and the target Docker volume to this container....