Bug 154325 - Unable to update my RedHat ES3 version with up2date
Unable to update my RedHat ES3 version with up2date
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: up2date (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bret McMillan
Fanny Augustin
Depends On:
  Show dependency treegraph
Reported: 2005-04-09 19:00 EDT by Nagarjun Chevula
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 15:04:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nagarjun Chevula 2005-04-09 19:00:25 EDT
Description of problem:
I got my new Linux desktop from Dell with RedHat ES 3. I am trying to find out
how to launch up2date to update software on my system. When I launch up2date I
get the following error:

Error Message:
    Service not enabled for system profile: "nagarjun"
Error Class Code: 31
Error Class Info: 
     This system does not have a valid entitlement for Red Hat Network.
     Please visit https://rhn.redhat.com/network/systems/entitlements.pxt
     or login at https://rhn.redhat.com, and from the "Systems" tab,
     select "System Entitlements" to enable RHN service for this system.

I would appreciate your help.
Comment 1 Suzanne Hillman 2005-04-11 10:52:51 EDT
This is something for which you would be best off talking to support. 

Please call 800-REDHAT1 

or go to http://www.redhat.com/support
Comment 2 RHEL Product and Program Management 2007-10-19 15:04:53 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.