------------------------------
Hi - yes, RHN is aware that the current RHN Proxy code is not 100% compatible with the Red Hat Enterprise Linux 5 Beta 2 yum client. We are investigating and plan to have a solution, which customers can upgrade too, prior to the production release of Enterprise Linux 5.
Regards,
Cliff.
Message: 2
Date: Tue, 05 Dec 2006 11:46:42 -0500
From: Steven Lee <[EMAIL PROTECTED]>
Subject: Re: [rhelv5-beta-list] Updating Beta1 to Beta2 via RHN-Proxy
To: "Red Hat Enterprise Linux 5 (Tikanga) Beta releases discussion
mailing-list" <[email protected]>
Cc: RHEL Proxy Admin <[EMAIL PROTECTED]>, Resa Alvord
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
All,
Since I run Cornell's RHN proxy server, I can see how things break on
both sides :-)
On the RHEL 5 Desktop machine, I got the same error described below.
On the proxy server (version 4.1.0), I see the following errors in
rhn_proxy_broker.log:
---
2006/12/05 11:40:37 -04:00 3222 24.59.76.25:
proxy/apacheServer.__call__('New request, component proxy.broker',)
2006/12/05 11:40:37 -04:00 3222 24.59.76.25: broker/rhnBroker.handler
2006/12/05 11:40:37 -04:00 3222 24.59.76.25: proxy/rhnShared._serverCommo
2006/12/05 11:40:38 -04:00 3222 24.59.76.25:
broker/rhnBroker.handler('Leaving handler with status code 206',)
2006/12/05 11:40:38 -04:00 3222 24.59.76.25:
proxy/apacheHandler.handler('Leaving with status code 206',)
2006/12/05 11:40:38 -04:00 3222 24.59.76.25:
proxy/apacheHandler.cleanupHandler
---
So there seems to be a problem with RHN Proxy Server with RHEL 5. I
could update and install packages if I connect the RHEL 5 Desktop
directly to the RedHat Network.
Steven
--
Clifford Perry
Team Lead, RHN Sustaining Engineering
Red Hat, Inc.
http://www.redhat.com/
+1 919 754 4403
RHCE# 803004507210710
_______________________________________________
rhelv5-beta-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-beta-list
