Description of problem:
When i try to run up to date i get the following error:
Please run rhn_register (or up2date --register on Red Hat Linux 8.0)
as root on this client
Error Class Code: 9
Error Class Info: Invalid System Credentials.
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.
Version-Release number of selected component (if applicable):
I have update version up2date-4.0.1-1, which wants to be updated to
version up2date-4.2.5-1. I can only find older versions on the redhat
Steps to Reproduce:
1.redhat aler notification tool
2.click on "launch up2date" button
The system is registered on the RHN website. I am root when i try to
run up2date. I am new to linux. system is registered as Red Hat
Enterprise Linux WS (v. 3 for x86)
How did you become root? Log in as such, or 'su' to it?
I logged straight into root. Although, i have entered the root
password while logged in as another persona. In either case i get the
same update error.
The error indicates the systemid sent up identifying the client
doesn't match anything in the database.
If you have changed to serverUrl (to point at a RHN Sattellite
for example) could be a cause. So verify serverURL in
/etc/sysconfig/rhn/up2date is pointing at
also, if you could give me your RHN username, I can try
to verify the server is registered properly.
The URL above is the serverURL is see in the file. my RHN user name is
*** Bug 160583 has been marked as a duplicate of this bug. ***
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.