RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Hi,

I am having issue when activating the RH6, here is what I am getting:

[root@vserkt467 ~]# rhnreg_ks --activationkey=677c51c9677f5c51

Error Message:
    Could not find token '677c51c9677f5c51'
Error Class Code: 60
Error Class Info: Invalid system registration token
Explanation:
     An error has occurred while processing your request. If this problem
     persists please enter a bug report at bugzilla.redhat.com.
     If you choose to submit the bug report, please be sure to include
     details of what you were trying to do when this error occurred and
     details on how to reproduce this problem.


What are we doing wrong?

Thanks.

This has, however, nothing to do with the acl package I am afraid.

Reassigning to rhn-client-tools...

Is this registration against RHN or RHN Satellite?

Also, are you sure the activation key is correct? Activation keys
you create in RHN webui are 32 chars long. Satellite activation keys are
usually of the form: org-key (e.g. 1-afefc72b02c04a4e91f9e4ed7a305d87).

This was the only number it was given to me. How to obtain the correct activation key?

Thanks.

You create an activation key in RHN's webui and pass it to
rhnreg_ks --activationkey=...

Though what you're showing above is certainly not an activation key.

My wild guess would be that the 16-char string is a subscription number
you'll use for activation at http://www.redhat.com/activate

This number appears to be subscription number used for the installation. I guess there is no issue then.

My recommendation at this point would be to contact Red Hat Customer Support
to assist you with this issue.

Thank you.