[Spacewalk-list] Spacewalk proxy connection problem after upgrade to 2.0

Wed Aug 28 16:43:32 UTC 2013

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
________________________________
Von: Boyd, Robert<mailto:Robert.Boyd at peoplefluent.com>
Gesendet: ‎28.‎08.‎2013 17:34
An: spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>
Betreff: Re: [Spacewalk-list] Spacewalk proxy connection problem after upgrade to 2.0

Is your proxy server properly registered as a client and proxy server with the master?

-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Speigner Thomas
Sent: Wednesday, August 28, 2013 8:08 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Spacewalk proxy connection problem after upgrade to 2.0

Hi,

I have tried the proxy to master connection with and without SSL. Same problem. I can trace the request through the proxy server to the master server and the master server handles the request. I don't know if the answer back is right ...

When I register the endpoint to the master server all goes fine. But I can't register it back to the proxy server ... neither http://<server>:80/XMLRPC nor https://<server>:443/XMLRPC.

I always get a traceback ...

kind regards ...

Thomas SPEIGNER

__________________________________________________

-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Stuart Green
Sent: Tuesday, August 27, 2013 4:05 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Spacewalk proxy connection problem after upgrade to 2.0

If you put :443 in the actual server name, have you tried without?

Stu

On 27/08/2013 14:52, sebastien foucou wrote:
> Speigner Thomas <Thomas.Speigner at ...> writes:
>
>>
>>
>> Hi everyone,
>>
>> We upgraded Spacewalk to version 2.0. the master instance looks fine
>> and
> everything looks fine.
>> But we have problems after upgrade of the proxy instance in our
> datacenter.
>> Now all servers behind the proxy are not able to query the master
>> instance
> with error: “XMLRPC ProtocolError: <ProtocolError for ***proxy*** /XMLRPC:
> 500 Internal Server Error>”
>>
>> [snip]
>>
>> We uninstalled/installed/configured the Spacewalk proxy again without
> luck.
>> Anyone with the same error?
>>
>> kind regards ...Thomas SPEIGNER
>>
> Hello
>
> I updated my platefome spacewalk in version 2.0:
> the main server and the proxy.
>
> I have the following problem on the proxy, so that everything works on
> the primary server:
>
> in /var/log/httpd/error_log
>
> Exception reported from spwkf1p1
> Time: Tue Aug 27 15:28:17 2013
> Exception type exceptions.KeyError
> Exception while handling function handler Request object information:
> URI: /XMLRPC
> Remote Host: 172.xxx.xxx.xxx
> Server Name: spwkf1p1:443
> Headers passed in:
>          Accept-Encoding: identity
>          Content-Length: 2718
>          Host: spwkf1p1:443
>          content-type: text/xml
>          user-agent: rhn.rpclib.py/$Revision$
>          x-client-version: 1
>          x-info: RPC Processor (C) Red Hat, Inc (version $Revision$)
>          x-rhn-client-capability:
> packages.verify(1)=1,packages.extended_profile(2)=1,configfiles.base64
> _enc(1
> )=1,reboot.reboot(1)=1,configfiles.deploy(1)=1,caneatCheese(1)=1,packa
> ges.ro
> llBack(1)=1,configfiles.mtime_upload(1)=1,configfiles.diff(1)=1,packag
> es.upd
> ate(2)=2,script.run(1)=1,configfiles.upload(1)=1,packages.runTransacti
> on(1)=
> 1,packages.verify(1)=1,packages.extended_profile(2)=1,configfiles.base
> 64_enc
> (1)=1,reboot.reboot(1)=1,configfiles.deploy(1)=1,caneatCheese(1)=1,packages.
> rollBack(1)=1,configfiles.mtime_upload(1)=1,configfiles.diff(1)=1,pack
> ages.u
> pdate(2)=2,script.run(1)=1,configfiles.upload(1)=1,packages.runTransac
> tion(1
> )=1
>          x-rhn-transport-capability: follow-redirects=3
>          x-transport-info: Extended Capabilities Transport (C) Red
> Hat, Inc (version $Revision$)
>          x-up2date-version: 1.7.14-1.el5 Extra information about this
> error:
> Unhandled exception type
>
> Exception Handler Information
> Traceback (most recent call last):
>    File "/usr/share/rhn/proxy/apacheServer.py", line 62, in __call__
>      ret = f(req)
>    File "/usr/share/rhn/proxy/apacheHandler.py", line 355, in handler
>      ret = handlerObj.handler()
>    File "/usr/share/rhn/proxy/broker/rhnBroker.py", line 215, in handler
>      status = self._serverCommo()       # part 2
>    File "/usr/share/rhn/proxy/rhnShared.py", line 201, in _serverCommo
>      status, headers, bodyFd = self._proxy2server()
>    File "/usr/share/rhn/proxy/rhnShared.py", line 366, in _proxy2server
>      http_connection.send(self.req.headers_in['wsgi.input'])
> KeyError: 'wsgi.input'
>
> Exception reported from spwkf1p1
> Time: Tue Aug 27 15:36:20 2013
>
> My server is "CentOS release 5.9 (Final)"
>
>
> _______________________________________________
> 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

_______________________________________________
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/20130828/15cde979/attachment.htm>