Bug 22785 - Fata Error Communicating With Server
Summary: Fata Error Communicating With Server
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Preston Brown
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-23 20:46 UTC by David Highley
Modified: 2007-04-18 16:30 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2000-12-27 21:56:33 UTC


Attachments (Terms of Use)

Description David Highley 2000-12-23 20:46:04 UTC
Updated program up2date with the following rpms:
i386:
ftp://updates.redhat.com/6.2/i386/up2date-2.1.7-0.6.x.i386.rpm
ftp://updates.redhat.com/6.2/i386/up2date-gnome-2.1.7-0.6.x.i386.rpm
ftp://updates.redhat.com/6.2/i386/python-xmlrpc-1.2.1-0.6.x.i386.rpm
ftp://updates.redhat.com/6.2/i386/python-1.5.2-27.6.x.i386.rpm

noarch:
ftp://updates.redhat.com/6.2/noarch/rhn_register-1.0.2-0.6.x.noarch.rpm
ftp://updates.redhat.com/6.2/noarch/rhn_register-gnome-1.0.2-0.6.x.noarch.rpm

First ran into the confusion about whether the product had been registered.
So I
tried to re-register the product which failed because it was all ready
registered.

Tried an anonymous down load and foud that the registration was found, but
the
down load fails.

Error is:
There was a fatal error communicating with the server. The message was:
invalid Architecture and OS release combination

Comment 1 Preston Brown 2000-12-27 21:56:30 UTC
Has the problem persisted?


Comment 2 Preston Brown 2001-02-09 05:32:02 UTC
closed due to lack of feedback and inability to duplicate; lack of other similar
reports.


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