Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 61638 - error while connecting to RHN
error while connecting to RHN
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Jay Turner
: 61655 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2002-03-22 09:32 EST by Need Real Name
Modified: 2015-01-07 18:55 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-05-22 09:09:42 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 Need Real Name 2002-03-22 09:32:44 EST
while doing "up2date -l", i received the following error:
fatal error while communication server, the error message was
Version-Release number of selected component (if applicable):

How Reproducible: all the time

Steps to Reproduce:
1. type "up2date -l"
2. or "up2date -u -i up2date"
3. and same error appear when tried to update certain packages.

Actual Results: see problem description above

Expected Results:

Additional Information:
Comment 1 Jay Turner 2002-03-22 14:24:20 EST
*** Bug 61655 has been marked as a duplicate of this bug. ***
Comment 2 Need Real Name 2002-03-22 17:28:17 EST
i think i've found the fix. the problem can be solved by upgrade
up2date the the newest version--up2date-gnome-2.7.11-7.x.1.
since the old up2date won't work, you can't simply do "up2date -u up2date",
you have to download the new up2date rpm and upgrade it by hand.
after you install the new up2date, it should work just fine.
Comment 3 Adrian Likins 2002-03-25 18:53:05 EST
The 404 error message a temporary server error. It should be fixed now.
Comment 4 Matt Jamison 2003-05-22 09:09:42 EDT
fixed. resolving bug.

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