[Spacewalk-list] Yum Fails For Clients Behind Proxy

Thu May 15 03:36:34 UTC 2014

So here's some useful information.  One of my colleagues found out the pycurl has an issue with using https.  So I changed the proxy to http:// and not https:// and everything started working!  Apparently this issue is only existent in an older version of PyCurl, but I'm using the one that Spacewalk installed. :(

Thanks for everybody's help!  Really appreciate it!

Regards,

Nick Kitmitto
System Engineer
ClearDATA
Healthcare Cloud Computing
and Information Security
602-635-4004 24x7 Help Line
www.cleardata.net<http://www.cleardata.net/>

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Coffman, Anthony J
Sent: Wednesday, May 14, 2014 1:34 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Yum Fails For Clients Behind Proxy

Check the squid access log on the proxy.  At the point where this error was generated - it was trying to pull the repomd file from the Spacewalk master via the Squid on the proxy.  That log should have something relevant in it for this attempt.

Also - make sure squid is running on the proxy using the "rhn-proxy status" command.

--Tony

From: spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com> [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Nick Kitmitto
Sent: Wednesday, May 14, 2014 1:28 AM
To: spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>
Subject: [Spacewalk-list] Yum Fails For Clients Behind Proxy

I recently setup proxy servers and got them functional and registered properly through Spacewalk.  I can now use the proxy servers to register the clients in the respective datacenter, however when I try to install with yum, it fails.  Is there something I need to do to the proxy servers so they start handing out packages that are in the repos on the master?

Here's the error on the client:

[root at hostname rhn]# yum repolist
Loaded plugins: fastestmirror, rhnplugin, security
This system is receiving updates from RHN Classic or Red Hat Satellite.
Determining fastest mirrors
repo id                                                                          repo name                                                                        status
centos-base-64bit                                                                CentOS Base 64Bit                                                                0
epel-64bit                                                                       EPEL 64Bit                                                                       0
repolist: 0
[root at hostname rhn]# yum install xclock
Loaded plugins: fastestmirror, rhnplugin, security
This system is receiving updates from RHN Classic or Red Hat Satellite.
Loading mirror speeds from cached hostfile
Error: Cannot retrieve repository metadata (repomd.xml) for repository: centos-base-64bit. Please verify its path and try again

Here's what I see on the proxy:

==> ssl_access_log <==
10.210.0.70 - - [13/May/2014:22:26:32 -0700] "POST /XMLRPC HTTP/1.1" 200 2042

==> ssl_request_log <==
[13/May/2014:22:26:32 -0700] 10.210.0.70 TLSv1.2 DHE-RSA-AES256-GCM-SHA384 "POST /XMLRPC HTTP/1.1" 2042

==> ssl_access_log <==
10.210.0.70 - - [13/May/2014:22:26:32 -0700] "POST /XMLRPC HTTP/1.1" 200 1103

==> ssl_request_log <==
[13/May/2014:22:26:32 -0700] 10.210.0.70 TLSv1.2 DHE-RSA-AES256-GCM-SHA384 "POST /XMLRPC HTTP/1.1" 1103

==> ssl_access_log <==
10.210.0.70 - - [13/May/2014:22:26:33 -0700] "POST /XMLRPC HTTP/1.1" 200 1103

==> ssl_request_log <==
[13/May/2014:22:26:33 -0700] 10.210.0.70 TLSv1.2 DHE-RSA-AES256-GCM-SHA384 "POST /XMLRPC HTTP/1.1" 1103

==> ssl_access_log <==
10.210.0.70 - - [13/May/2014:22:26:33 -0700] "POST /XMLRPC HTTP/1.1" 200 1103

==> ssl_request_log <==
[13/May/2014:22:26:33 -0700] 10.210.0.70 TLSv1.2 DHE-RSA-AES256-GCM-SHA384 "POST /XMLRPC HTTP/1.1" 1103

Here's what I see on the master:

[13/May/2014:22:26:34 -0700] 10.209.0.86 TLSv1.2 DHE-RSA-AES256-GCM-SHA384 "POST /XMLRPC HTTP/1.1" 2042
[13/May/2014:22:26:34 -0700] 10.209.0.86 TLSv1.2 DHE-RSA-AES256-GCM-SHA384 "POST /XMLRPC HTTP/1.1" 1103
[13/May/2014:22:26:35 -0700] 10.209.0.86 TLSv1.2 DHE-RSA-AES256-GCM-SHA384 "POST /XMLRPC HTTP/1.1" 1103
[13/May/2014:22:26:35 -0700] 10.209.0.86 TLSv1.2 DHE-RSA-AES256-GCM-SHA384 "POST /XMLRPC HTTP/1.1" 1103

Thanks in advance if you're able to help!

Regards,

Nick Kitmitto
System Engineer
ClearDATA
Healthcare Cloud Computing
and Information Security
602-635-4004 24x7 Help Line
www.cleardata.net<http://www.cleardata.net/>

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20140515/3082fc35/attachment.htm>