Thanks Patrick. That fixed the issue for me as well. Greg Wojtak Sr. Unix Systems Engineer Office: (313) 373-4306 Cell: (734) 718-8472
On 2012-11-13 3:36 AM, "Patrick Hurrelmann" <[email protected]> wrote: >On 13.11.2012 09:29, Patrick Hurrelmann wrote: >> On 13.11.2012 03:44, Wojtak, Greg (Superfly) wrote: >>> No, these are the RHN plugin repos. My CentOS, spacewalk, and epel >>>repo files are all enabled = 0. I got back to my desk this evening and >>>saw someone had posted the message in chat: >>> >>> "I have an odd problem with my proxies since upgrading to 1.8. Since >>>the repo sync ran, no system registered through a proxy can do updates >>>on my EPEL or SW client channels. I get 404s from the proxy. Systems >>>registered directly to my SW server are fine. Anyone else seen this?" >>> >>> This is exactly what I am seeing - it is only the spacewalk client and >>>epel repos. CentOS updates and base channels are providing packages >>>just fine through the proxy. Seems I'm not the only one having this >>>problem. >>> >> >> Hi, >> >> I'm seeing the same after update to 1.8. Tried a full proxy reinstall, >> but the result is the same. For me all channels are affected. (centos 6, >> base, updates, fasttrack). >> >> Right now every attempt to download a package behind the proxy results >> in an "Forwarding loop" logged by squid in cache.log. >> >> Sample: >> >> 2012/11/13 09:03:06| WARNING: Forwarding loop detected for: >> GET >> /XMLRPC/$RHN/centos6.3-fasttrack-x86_64/listAllPackages/20121113033544 >> HTTP/1.1 >> Host: 127.0.0.1 >> Accept-Encoding: identity >> X-RHN-IP-Path: 127.0.0.1 >> X-Info: RPC Processor (C) Red Hat, Inc (version 2.5.55-1.el6) >> User-Agent: rhn.rpclib.py/2.5.55-1.el6 >> X-RHN-Auth-Server-Time: 1352793786.05 >> X-RHN-Transport-Capability: follow-redirects=3 >> Accept-Encoding: identity >> X-RHN-Auth-Expire-Offset: 3600.0 >> X-RHN-Proxy-Version: 5.5.0 >> X-Transport-Info: Extended Capabilities Transport (C) Red Hat, Inc >> (version 2.5.55-1.el6) >> Connection: keep-alive >> Via: 1.1 proxy.xxx.com (squid/3.1.10) >> X-RHN-Auth: xxx >> X-Client-Version: 1 >> X-RHN-Server-Id: 1000010029 >> X-RHN-Proxy-Auth: 1000010056::1352741575.19:21600.0:xxx:127.0.0.1 >> X-Forwarded-For: 127.0.0.1 >> Content-Type: text/xml >> Cache-Control: max-age=31536000 >> X-RHN-Auth-User-Id: >> >> >> Regards >> Patrick >> > >Solved :) > >I could find a BZ for the issue: >https://bugzilla.redhat.com/show_bug.cgi?id=872721 and the corresponding >fix in the following commit: >http://git.fedorahosted.org/cgit/spacewalk.git/commit/?id=5f00038675c58c5a >401d0c4a5cbfa332c28a4405 > >After applying the patch locally my proxy is working as expected again. >Yum update is finally working again. > >Regards >Patrick > >-- >Lobster LOGsuite GmbH, Münchner Straße 15a, D-82319 Starnberg > >HRB 178831, Amtsgericht München >Geschäftsführer: Dr. Martin Fischer, Rolf Henrich > >_______________________________________________ >Spacewalk-list mailing list >[email protected] >https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
