Bug 1002007
Summary: | proxy "Exception type exceptions.KeyError" and "XMLRPC ProtocolError" | |||
---|---|---|---|---|
Product: | [Community] Spacewalk | Reporter: | Sebastien Foucou <admin.systeme> | |
Component: | Proxy Server | Assignee: | Michael Mráka <mmraka> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Satellite QA List <satqe-list> | |
Severity: | urgent | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 2.0 | CC: | admin.systeme, cperry, lpramuk, mmraka | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | spacewalk-proxy-2.0.2-1 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1002441 (view as bug list) | Environment: | ||
Last Closed: | 2013-12-19 11:58:43 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 991452 |
Description
Sebastien Foucou
2013-08-28 10:13:06 UTC
The broker is not broking, /etc/httpd/error_log: 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 348, in handler handlerObj = rhnBroker.BrokerHandler(req) File "/usr/share/rhn/proxy/broker/rhnBroker.py", line 70, in __init__ my_ip_addr = req.headers_in['SERVER_ADDR'] KeyError: 'SERVER_ADDR' Oops. I meant /var/log/httpd/error_log: Lukas, can you tell me specifically what you did to get that error? client -> proxy (el5) -> satellite [@client]# rhnreg_ks --username=$USER --password=$PASS --serverUrl=https://$PROXY/XMLRPC --sslCACert=/usr/share/rhn/${PROXY}-TRUSTED-SSL-CERT --force An error has occurred: Error communicating with server. The message was: Internal Server Error See /var/log/up2date for more information /var/log/up2date: ... File "/usr/share/rhn/up2date_client/rhnserver.py", line 160, in __get_capabilities self.registration.welcome_message() File "/usr/share/rhn/up2date_client/rhnserver.py", line 51, in __call__ return rpcServer.doCall(method, *args, **kwargs) File "/usr/share/rhn/up2date_client/rpcServer.py", line 278, in doCall raise up2dateErrors.CommunicationError(e.errmsg) <class 'up2date_client.up2dateErrors.CommunicationError'>: Error communicating with server. The message was: Internal Server Error I changed proxy spec to use mod_wsgi on RHEL5 but there are still some issues; investigating difference between RHEL6 and RHEL5... commit 34c3e9c2c0177345a8f0c0ce2a2a9757e136ec67 1002007 - use mod_wsgi even on RHEL5 Fixed python 2.4 httplib issues in Spacewalk master: commit dafdc3d2245f8f8ec02ddbe92be316a3ab2505a8 Automatic commit of package [spacewalk-proxy] release [2.1.9-1]. commit cd5f85734304214dc40470b5e4ef6b96c89ffc47 1002007 - don't send empty data addressing 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/redirect/rhnRedirect.py", line 92, 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 370, in _proxy2server http_connection.send(data) File "/usr/lib64/python2.4/httplib.py", line 664, in send self.sock.sendall(str) File "/usr/lib/python2.4/site-packages/rhn/SSL.py", line 217, in write sent = self._connection.send(data) SysCallError: (-1, 'Unexpected EOF') Oops, pylint fix commit eaaa9d48395d4b1b706ee0b48d366f66e9926fda fixed pylint error Hi, I started this morning an update proxy First, i installed and activated the mod_wsgi module for apache Second, i installed the proxy update The installed version is repository "nightly": spacewalk-ssl-cert-check-2.3-1.el5 spacewalk-proxy-broker-2.1.10-1.el5 spacewalk-proxy-docs-2.0.1-1.el5 spacewalk-setup-jabberd-2.0.1-1.el5 spacewalk-base-minimal-config-2.1.16-1.el5 spacewalk-proxy-common-2.1.10-1.el5 spacewalk-proxy-management-2.1.10-1.el5 spacewalk-monitoring-selinux-2.0.1-1.el5 spacewalk-proxy-html-2.0.1-1.el5 spacewalk-proxy-selinux-2.0.1-1.el5 spacewalk-certs-tools-2.1.1-1.el5 spacewalk-base-minimal-2.1.16-1.el5 spacewalk-backend-2.1.14-1.el5 spacewalk-proxy-redirect-2.1.10-1.el5 spacewalk-proxy-monitoring-2.0.1-1.el5 spacewalk-backend-libs-2.1.14-1.el5 spacewalk-proxy-installer-2.1.1-1.el5 spacewalk-proxy-package-manager-2.1.10-1.el5 I unsubscribed the proxy server on spacewalk : # rhn-proxy-activate --deactivate I started the proxy configuration: # /usr/sbin/configure-proxy.sh I did a test from a client and everything works perfectly now. Thank you very much for your help! NB: the spacewalk server remained in version 2.0, do you recommend an update to 2.1? (In reply to Sebastien Foucou from comment #9) > Hi, > > I started this morning an update proxy ... > I did a test from a client and everything works perfectly now. > > Thank you very much for your help! > > NB: the spacewalk server remained in version 2.0, do you recommend an update > to 2.1? Hello Sebastien, Thank you for reporting back. Please do not upgrade your server, current nightly version is not supposed to be stable and there might not be an easy way to upgrade to final 2.1 once it will be released. Conversely we feel this is a serious bug and we work on backporting it to current 2.0 proxy version. Regards, Michael The fixed version spacewalk-proxy-2.0.2-1 has been released as a part of Spacewalk 2.0 release. If the solution does not work for you, please open a new bug report. |