Bug 432358
| Summary: | yum process not functional through proxy appliance | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Don Vanco <don.vanco> |
| Component: | yum-rhn-plugin | Assignee: | John Matthews <jmatthew> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.1 | CC: | Ben.Stanley, cperry, cww, etay, johfulto, ppira, xdmoon |
| Target Milestone: | rc | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-02-21 04:31:50 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Don Vanco
2008-02-11 15:27:10 UTC
Have the exact same problem. Also with a Bluecoat proxy appliance. Tried updating m2crypto to the latest version from FasTrack but it made no difference, still "Connection reset by peer". We had this problem. We sent off a packet capture to BlueCoat and they recommended some changes to us. I don't know what the changes were, I will try to get them attached here. However, as a result of the changes, I am now successfully running 'yum update'. This bug is BlueCoat's fault. So - some random user comes in here and says "it's BlueCoat's fault", posts no resolution for the world at large, and the bug gets closed as "not a bug"?? I spoke with BlueCoat - they have no idea what the problem is and have never seen it before. Until someone PROVES otherwise please leave this as an open bug. As up2date from RedHat Enterprise 4 works fine with our bluecoat proxy and yum with rhnplugin from RedHat Enterprise 5 does not, rhnplugin must do things a bit different than the old up2date. According to our network guys rhnplugin uses TLS instead of SSL and that's why bluecoat resets the connection, they did not manage to get the bluecoat proxy to let TLS through though (yet). The following is the information forwarded to me by the local BlueCoat
administrator. I have no further information, for which I refer you to BlueCoat
systems.
The issue was apparently software bug: 94037 where the compression method for
the website is not supported by the proxy.
This was the fix:
1) Disable protocol detection
Go to Management console > Configuration > Policy > Policy Files Install
Local File From > Text Editor
<proxy>
url.domain = //redhat.com detect_protocol(no)
2) Disable HTTP server compression
Web access layer:
Add a rule:
Source: Any
Destination: Right click > Set > New > Request URL > Simple match > redhat.com
Service: Any
Time: Any
Action: Right click > New > Set Server HTTP Compression Object >Disable
HTTP compression
This worked for us.
Above fix works for me too. Not a bug in rhnplugin, more of a documentation bug as rhnplugin differs a bit from up2date. Can we have this documented in the knowledge base? This was sent to our knowledgebase team as a suggested article. It does not seem to have been done yet. I am though going to close this bug out now. A search for BlueCoat should quickly find this bug report in public archives for future users as well. Cliff (In reply to comment #10) KBase article at http://kbase.redhat.com/faq/docs/DOC-17129 (In reply to comment #11) > (In reply to comment #10) > KBase article at http://kbase.redhat.com/faq/docs/DOC-17129 (It's currently undergoing the publication process.) |