[Spacewalk-list] Yum Fails For Clients Behind Proxy

Thomas Foster thomas.foster80 at gmail.com
Wed May 14 16:55:41 UTC 2014


syn_sent on the server means that a firewall is blocking the communication
to the server...check firewall rules.


On Wed, May 14, 2014 at 12:48 PM, Matthew Madey <mattmadey at gmail.com> wrote:

> Look for any errors in apache error or access log on the proxy. I ran into
> a similar issue that turned out to be permissions related. Check
> permissions on /var/cache/run on the spacewalk server. Should be owned by
> apache.root
> On May 14, 2014 12:33 AM, "Nick Kitmitto" <nick.kitmitto at cleardata.com>
> wrote:
>
>>  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
>>
>> *Clear**DATA*
>>
>> Healthcare Cloud Computing
>>
>> and Information Security
>>
>> 602-635-4004 24x7 Help Line
>>
>> 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.
>>
>>
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20140514/5bc3629e/attachment.htm>


More information about the Spacewalk-list mailing list