Red Hat Satellite 5 recieves traceback email with an error 'Invalid request received (function: proxy.checkTokenValidity invalid).'

Solution Verified - Updated -

Environment

  • Red Hat Satellite 5
  • Red Hat Proxy server

Issue

  • Since renaming hostname and changing the IP of a Red Hat Proxy , Red Hat Satellite 5 is receiving trackback emails indicating errors.
  • Red Hat Satellite server is receiving traceback emails 
Exception reported from satellite.example.com
Time: Sun Jan 17 08:51:37 2016
Exception type <class 'spacewalk.server.apacheRequest.UnknownXML'>
Exception while handling function proxy.checkTokenValidity Request object information:
URI: /XMLRPC
Remote Host: 10.0.0.1
Server Name: satellite.example.com:443
Headers passed in:
    Accept-Encoding: identity
    CONTENT_LENGTH: 2706
    CONTENT_TYPE: text/xml
    DOCUMENT_ROOT: /var/www/html
    GATEWAY_INTERFACE: CGI/1.1
    HTTPS: 1
    HTTP_ACCEPT_ENCODING: identity
    HTTP_HOST: satellite.example.com
    HTTP_USER_AGENT: rhn.rpclib.py/$Revision$
    HTTP_X_CLIENT_VERSION: 1
    HTTP_X_INFO: RPC Processor (C) Red Hat, Inc (version $Revision$)
    HTTP_X_RHN_CLIENT_VERSION: 2
    HTTP_X_RHN_TRANSPORT_CAPABILITY: follow-redirects=3
    HTTP_X_TRANSPORT_INFO: Extended Capabilities Transport (C) Red Hat, Inc (version $Revision$)
    Host: satellite.example.com
    PATH_INFO: 
    QUERY_STRING: 
    REMOTE_ADDR: 10.0.36.139
    REMOTE_PORT: 47532
    REQUEST_METHOD: POST
    REQUEST_URI: /XMLRPC
    SCRIPT_FILENAME: /usr/share/rhn/wsgi/xmlrpc.py
    SCRIPT_NAME: /XMLRPC
    SCRIPT_URI: https://satellite.example.com/XMLRPC
    SCRIPT_URL: /XMLRPC
    SERVER_ADDR: 10.0.40.69
    SERVER_ADMIN: root@localhost
    SERVER_NAME: satellite.example.com
    SERVER_PORT: 443
    SERVER_PROTOCOL: HTTP/1.1
    SERVER_SIGNATURE: <address>Apache Server at satellite.example.com Port 443</address>

    SERVER_SOFTWARE: Apache
    User-Agent: rhn.rpclib.py/$Revision$
    X-Client-Version: 1
    X-Info: RPC Processor (C) Red Hat, Inc (version $Revision$)
    X-RHN-Client-Version: 2
    X-RHN-Transport-Capability: follow-redirects=3
    X-Transport-Info: Extended Capabilities Transport (C) Red Hat, Inc (version $Revision$)
    mod_ssl.is_https: <built-in method ssl_is_https of mod_wsgi.Adapter object at 0x7f65585a9030>
    mod_ssl.var_lookup: <built-in method ssl_var_lookup of mod_wsgi.Adapter object at 0x7f65585a9030>
    mod_wsgi.application_group: satellite.example.com|/xmlrpc
    mod_wsgi.callable_object: application
    mod_wsgi.handler_script: 
    mod_wsgi.input_chunked: 0
    mod_wsgi.listener_host: 
    mod_wsgi.listener_port: 443
    mod_wsgi.process_group: 
    mod_wsgi.request_handler: wsgi-script
    mod_wsgi.script_reloading: 1
    mod_wsgi.version: (3, 2)
    wsgi.errors: <mod_wsgi.Log object at 0x7f6558355f30>
    wsgi.file_wrapper: <built-in method file_wrapper of mod_wsgi.Adapter object at 0x7f65585a9030>
    wsgi.input: <mod_wsgi.Input object at 0x7f6558355f70>
    wsgi.multiprocess: True
    wsgi.multithread: False
    wsgi.run_once: False
    wsgi.url_scheme: https
    wsgi.version: (1, 1)
Extra information about this error:
Response sent back to the caller:
While running 'proxy.checkTokenValidity': caught <class 'spacewalk.server.apacheRequest.UnknownXML'> : Invalid request received (function: proxy.checkTokenValidity invalid).



Exception Handler Information
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/spacewalk/server/apacheRequest.py", line 121, in call_function
    func = self.method_ref(method)
  File "/usr/lib/python2.6/site-packages/spacewalk/server/apacheRequest.py", line 452, in method_ref
    raise UnknownXML("function: %s invalid" % (method,))
UnknownXML: Invalid request received (function: proxy.checkTokenValidity invalid).

Resolution

  • To resolve this issue, try to sync the Red Hat Proxy server profile with Red Hat Satellite 5 server. 
# rhn-profile-sync
  • After syncing Red Hat Proxy profile, check whether Red Hat Satellite 5 is still receiving the traceback emails or not.
  • If Red Hat Satellite 5 is still receiving the traceback emails, try to reregister the Red Hat Proxy server with Red Hat Satellite 5 server.
  • After re-registering the Proxy server, reactivate the Proxy server.

Root Cause

  • Red Hat Satellite 5 generates the token for its communication with Red Hat Proxy server. This token requires a hostname of Red Hat Proxy server.
  • Red Hat Satellite fetches this information from the database. This information is provided by the client system to the satellite in reference to the systemid file.
  • This issue occurs when hostname of the Red Hat Proxy server is not updated on the Red Hat Satellite, which causes Red Hat Satellite server to use an old hostname to generate a token for communication with Red Hat Proxy server.

Diagnostic Steps

  • Check the changed hostname of Red Hat Proxy server in /etc/sysconfig/network
$ cat /etc/sysconfig/network
HOSTNAME=proxy1.example.com
  • Verify the hostname in /etc/sysconfig/rhn/systemid file, which is used to register with Red Hat Satellite 5 server.
$ less /etc/sysconfig/rhn/systemid | grep rhp
<value><string>proxy2.example.com</string></value>
  • The Mismatch of this hostname cause Red Hat Satellite to send traceback emails to user.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.