<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1255"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang="DE-AT" link="blue" vlink="purple"> <div class="WordSection1"> Hi Robert,<o:p></o:p> <o:p> </o:p> sorry, misunderstood your question. So my proxy is connected with the spacewalk master and under proxy - activation I can see "This machine is currently a licensed Red Hat Proxy (v2.0).”<o:p></o:p> The setting in up2date looks ok.<o:p></o:p> Yum repolist –verbose gives me all subscribed channels<o:p></o:p> So I tried following.<o:p></o:p> Deleting the whole server (proxy server) from the Management. -> OK<o:p></o:p> Register the server with rhnreg_ks … at the spacewalk master -> OK, no proxy register available at the spacewalk management for this server<o:p></o:p> rerun configure-proxy.sh at proxysite -> OK, now proxy register is available at the spacewalk management for the server. Same line as above.<o:p></o:p> Tried some commands rhn_checks, rhn-profile-sync, yum repolist –verbose … all seems fine.<o:p></o:p> <o:p> </o:p> Connected now to another server behind the proxy - all commands failed:<o:p></o:p> [root@test2 ~]$ rhn_check<o:p></o:p> XMLRPC ProtocolError: <ProtocolError for proxy.domain.lokal /XMLRPC: 500 Internal Server Error><o:p></o:p> [root@test2 ~]$ rhnreg_ks --serverUrl=https:// proxy.domain.lokal/XMLRPC --activationkey=my-actkey --force<o:p></o:p> An error has occurred:<o:p></o:p> Error communicating with server. The message was:<o:p></o:p> Internal Server Error<o:p></o:p> See /var/log/up2date for more information<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Content of /var/log/up2date<o:p></o:p> [Thu Aug 29 08:39:31 2013] up2date A protocol error occurred: Internal Server Error , attempt #1,<o:p></o:p> [Thu Aug 29 08:39:31 2013] up2date<o:p></o:p> Traceback (most recent call last):<o:p></o:p> File "/usr/sbin/rhnreg_ks", line 218, in <module><o:p></o:p> cli.run()<o:p></o:p> File "/usr/share/rhn/up2date_client/rhncli.py", line 96, in run<o:p></o:p> sys.exit(self.main() or 0)<o:p></o:p> File "/usr/sbin/rhnreg_ks", line 90, in main<o:p></o:p> rhnreg.getCaps()<o:p></o:p> File "/usr/share/rhn/up2date_client/rhnreg.py", line 248, in getCaps<o:p></o:p> s.capabilities.validate()<o:p></o:p> File "/usr/share/rhn/up2date_client/rhnserver.py", line 178, in __get_capabilities<o:p></o:p> self.registration.welcome_message()<o:p></o:p> File "/usr/share/rhn/up2date_client/rhnserver.py", line 63, in __call__<o:p></o:p> return rpcServer.doCall(method, *args, **kwargs)<o:p></o:p> File "/usr/share/rhn/up2date_client/rpcServer.py", line 204, in doCall<o:p></o:p> ret = method(*args, **kwargs)<o:p></o:p> File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__<o:p></o:p> return self.__send(self.__name, args)<o:p></o:p> File "/usr/share/rhn/up2date_client/rpcServer.py", line 38, in _request1<o:p></o:p> ret = self._request(methodname, params)<o:p></o:p> File "/usr/lib/python2.6/site-packages/rhn/rpclib.py", line 384, in _request<o:p></o:p> self._handler, request, verbose=self._verbose)<o:p></o:p> File "/usr/lib/python2.6/site-packages/rhn/transports.py", line 171, in request<o:p></o:p> headers, fd = req.send_http(host, handler)<o:p></o:p> File "/usr/lib/python2.6/site-packages/rhn/transports.py", line 730, in send_http<o:p></o:p> response.status, response.reason, response.msg)<o:p></o:p> <class 'up2date_client.up2dateErrors.CommunicationError'>: Error communicating with server. The message was:<o:p></o:p> Internal Server Error<o:p></o:p> <o:p> </o:p> I will now try to go back to 1.9 with proxy server …<o:p></o:p> <o:p> </o:p> <div> kind regards ...<o:p></o:p> <o:p> </o:p> Thomas SPEIGNER<o:p></o:p> <o:p> </o:p> __________________________________________________<o:p></o:p> </div> <o:p> </o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: spacewalk-list-bounces@redhat.com [mailto:spacewalk-list-bounces@redhat.com] On Behalf Of Boyd, Robert Sent: Thursday, August 29, 2013 12:20 AM To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Spacewalk proxy connection problem after upgrade to 2.0<o:p></o:p> </div> </div> <o:p> </o:p> Thomas,<o:p></o:p> <o:p> </o:p> I’m not sure the answer you gave answers my question. My question is about the proxy server and how it’s registered to the spacewalk master server.<o:p></o:p> <o:p> </o:p> What happens when you do rhn_check at the proxy server?<o:p></o:p> <o:p> </o:p> When you look at the web interface, and click on the systems tab, and then click on the systems button in the left hand column and then click on proxy – what do you see with regard to your proxy server? Is it listed? And if it’s listed, when you click on the proxy server name, what do you see for “checked in” time? <o:p></o:p> <o:p> </o:p> Maybe you will have to re-register the proxy server as a client of the master. Are you familiar with using the rhnreg_ks with the –f flag?<o:p></o:p> <o:p> </o:p> rhnreg_ks --serverUrl=http://${SPACEWALK_SERVER}/XMLRPC --activationkey=my-wonderful-activation-key –f<o:p></o:p> <o:p> </o:p> Are the settings in your /etc/sysconfig/rhn/up2date still correct? <o:p></o:p> <o:p> </o:p> What do you see when logged onto the proxy server as root and you enter yum repolist --verbose ?<o:p></o:p> <o:p> </o:p> Robert<o:p></o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: <a href="mailto:spacewalk-list-bounces@redhat.com">spacewalk-list-bounces@redhat.com</a> [<a href="mailto:spacewalk-list-bounces@redhat.com">mailto:spacewalk-list-bounces@redhat.com</a>] On Behalf Of Speigner Thomas Sent: Wednesday, August 28, 2013 12:44 PM To: <a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a> Subject: Re: [Spacewalk-list] Spacewalk proxy connection problem after upgrade to 2.0<o:p></o:p> </div> </div> <o:p> </o:p> <div> <div> <div> At version 1.9 it was. Then the error with version 2.0.1. Now I am not able even to register at the proxy. Kind regards Speigner Thomas<o:p></o:p> </div> </div> <div> <div class="MsoNormal" align="center" style="text-align:center"> <hr size="2" width="100%" align="center"> </div> Von: <a href="mailto:Robert.Boyd@peoplefluent.com">Boyd, Robert</a> Gesendet: ý28.ý08.ý2013 17:34 An: <a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a> Betreff: Re: [Spacewalk-list] Spacewalk proxy connection problem after upgrade to 2.0<o:p></o:p> </div> </div> <div> Is your proxy server properly registered as a client and proxy server with the master? <o:p></o:p> </div> </div> </body> </html>