Cannot attach subscription to my registered RHEL 6.2

Latest response

Hello,

I've successfully registered my RHEL 6.2 system (I have to use this rather old version), but can't attach it to my subscription.

When I Run Auto-Attach in the Customer Portal it tells me "Subscriptions have been auto-attached successfully", but nothing changes. In a terminal on the machine subscription-manager subscribe --auto simply returns "Status: Not Subscribed". Finally, when I try subscription-manager subscribe --pool <someID>, I get "Too many content sets for certificate Red Hat Enterprise Linux Developer Suite. A newer client may be available to address this problem. See kbase ....". The Knowledge Base article suggest to upgrade my subscription-manager, but omits to say how. I failed to upgrade it via yum, but without a subscription I don't have any repos anyway.

As subscribing seems to be a substantial and common process, am I missing something obvious?

AV
Log in to join the conversation

Responses

CM Expert 1105 points
5 November 2016 12:14 PM

I had a similar issue like this a few weeks ago, this is what I had to run to get it to work:

Confirm subscriptions with the following command:

subscription-manager list –available

Run the following command then:

subscription-manager register --force

AV Newbie 15 points
6 November 2016 10:11 AM

Hi Christopher,

thanks for the tip, but registering the system wasn't the problem. I actually can't subscribe it (so subscription-manager register --force does work, but only registers, not subscribes).

DW Active Contributor 134 points
10 November 2016 10:33 AM

I have hit the same issue when try to register rhel6.2

[root@l111064 /]# subscription-manager register --force The system has been registered with id: xxxxxxxxxxxxxxxxx [root@l111064 /]# subscription-manager list +-------------------------------------------+ Installed Product Status +-------------------------------------------+

ProductName: Red Hat Enterprise Linux Server Version: 6.2
Arch: x86_64
Status: Not Subscribed
Starts:
Expires:

Ryan Sawhill's picture Red Hat Guru 3719 points
11 November 2016 12:10 AM

You need to either update packages by searching & downloading them from the Portal or by registering to RHN, i.e.:

  1. Disable RHSM plugin and make sure RHN plugin is enabled

    sed -i.bak /^enabled/s,1,0, /etc/yum/pluginconf.d/subscription-manager.conf
sed -i  /^enabled/s,0,1, /etc/yum/pluginconf.d/rhnplugin.conf

  2. Disable SSL for the RHN plugin to avoid cert issues (I can't remember if that's a problem in RHEL 6.2)

    sed -i.bak /^serverURL=/s,https,http, /etc/sysconfig/rhn/up2date

  3. Use rhn_register or rhnreg_ks to register with RHN

  4. Update RHSM

    yum update subscription-manager

  5. Switch back to RHSM

    mv -v /etc/sysconfig/rhn/up2date{.bak,}
mv -v /etc/yum/pluginconf.d/subscription-manager.conf{.bak,}
sed -i  /^enabled/s,1,0, /etc/yum/pluginconf.d/rhnplugin.conf

  6. Delete the system entry in RHN

DW Active Contributor 134 points
11 November 2016 1:39 AM

thanks, yesterday I have successfully Subscribed my client used the steps in Knowledge Base article https://access.redhat.com/node/129003 . and it's the similar theory with your steps，thanks anyway.

AV Newbie 15 points
13 November 2016 10:38 PM

Hi Ryan,

thanks for the detailed instructions! After I managed to update the subscription manager, I was able to attach the subscription.

When I updated it via RHN, I also had to set

useNoSSLForPackages=1

in /etc/sysconfig/rhn/up2date (see here), and make sure check the latest update package when registering with RHN (not the one for RHEL 6.2, but a more recent version).

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.