[Spacewalk-list] Question about OSAD and proxies

Tue Feb 24 15:41:24 UTC 2009

Hey guys,

I'm trying to set up a distributed Spacewalk setup to update and install
packages on our servers at work. Currently, I have a Spacewalk server up
and running, several clients connected to it, a Spacewalk proxy (which is
one of the clients) and several clients connecting to the Spacewalk proxy.
Osa-dispatcher is installed on the server, osad is installed on all
clients (including the proxy, of course).

All seems well, except for one thing:
When I schedule an install for one of the clients behind the proxy, the
event is never picked up. I tried debugging it via the osad logs, but they
are a bit too cryptic for me. Here is some of the stuff I snooped out.

On the proxy:

--- SNIP ---

2009-02-24 15:28:22 jabber_lib.process: select() returned
2009-02-24 15:28:22 jabber_lib.process: Reading 1024 bytes from ssl socket
2009-02-24 15:28:22 jabber_lib.process: Read 1 bytes
2009-02-24 15:28:30 jabber_lib.process: None
2009-02-24 15:28:30 jabber_lib.process: before select(); timeout None
2009-02-24 15:28:30 jabber_lib.process: select() returned
2009-02-24 15:28:30 jabber_lib.process: Reading 1024 bytes from ssl socket
2009-02-24 15:28:30 jabber_lib.process: Read 132 bytes
2009-02-24 15:28:30 jabber_lib._orig_dispatch: <error><conflict xmlns =
'urn:ietf:params:xml:ns:xmpp-streams'  /></error>
<-- <error><conflict xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' 
/></error>

2009-02-24 15:28:36 jabber_lib.process: None
2009-02-24 15:28:36 jabber_lib.process: before select(); timeout None
2009-02-24 15:28:36 jabber_lib.process: select() returned
2009-02-24 15:28:36 jabber_lib.process: Reading 1024 bytes from ssl socket
2009-02-24 15:28:36 jabber_lib.process: Read 16 bytes
2009-02-24 15:28:46 jabber_lib.process: None
2009-02-24 15:28:46 jabber_lib.process: before select(); timeout None
2009-02-24 15:28:46 jabber_lib.process: select() returned
2009-02-24 15:28:46 jabber_lib.process: Reading 1024 bytes from ssl socket
Error caught:
Traceback (most recent call last):
  File "/usr/share/rhn/osad/jabber_lib.py", line 123, in main
    self.process_forever(c)
  File "/usr/share/rhn/osad/jabber_lib.py", line 181, in process_forever
    self.process_once(client)
  File "/usr/share/rhn/osad/osad.py", line 242, in process_once
    client.process(timeout=None)
  File "/usr/share/rhn/osad/jabber_lib.py", line 1044, in process
    raise SSLError("OpenSSL error; will retry", str(e))
SSLError: ('OpenSSL error; will retry', "(-1, 'Unexpected EOF')")

--- SNIP ---

This seems to happen as soon as an event comes down from the Spacewalk
server, but I'm not too sure.

On one of the clients I found this remarkable (but I'm not sure, again):

$ cat /var/log/osad | grep error
2009-02-24 14:48:55 jabber_lib._orig_dispatch: <iq type='error'
id='auth-get-c702b1-3'><error code='401' /><query xmlns = 'jabber:iq:auth'
><username>osad-faea6db6be</username></query></iq>
2009-02-24 14:48:55 jabber_lib.dispatch: <iq type='error'
id='auth-get-c702b1-3'><error xmlns = 'jabber:client'  code='401' /><query
xmlns = 'jabber:iq:auth'
><username>osad-faea6db6be</username></query></iq>
2009-02-24 14:48:55 jabber_lib._get_callbacks: <iq type='error'
id='auth-get-c702b1-3'><error xmlns = 'jabber:client'  code='401' /><query
xmlns = 'jabber:iq:auth'
><username>osad-faea6db6be</username></query></iq>
2009-02-24 14:48:55 jabber_lib.dispatch: Unhandled stanza <iq type='error'
id='auth-get-c702b1-3'><error xmlns = 'jabber:client'  code='401' /><query
xmlns = 'jabber:iq:auth'
><username>osad-faea6db6be</username></query></iq>
2009-02-24 15:01:22 jabber_lib._orig_dispatch: <error><conflict xmlns =
'urn:ietf:params:xml:ns:xmpp-streams'  /></error>
2009-02-24 15:01:30 jabber_lib._orig_dispatch: <error><conflict xmlns =
'urn:ietf:params:xml:ns:xmpp-streams'  /></error>
2009-02-24 15:17:36 jabber_lib._orig_dispatch: <iq type='error'
id='auth-get-b193ee-0'><error code='401' /><query xmlns = 'jabber:iq:auth'
><username>osad-faea6db6be</username></query></iq>
2009-02-24 15:17:36 jabber_lib.dispatch: <iq type='error'
id='auth-get-b193ee-0'><error xmlns = 'jabber:client'  code='401' /><query
xmlns = 'jabber:iq:auth'
><username>osad-faea6db6be</username></query></iq>
2009-02-24 15:17:36 jabber_lib._get_callbacks: <iq type='error'
id='auth-get-b193ee-0'><error xmlns = 'jabber:client'  code='401' /><query
xmlns = 'jabber:iq:auth'
><username>osad-faea6db6be</username></query></iq>
2009-02-24 15:17:36 jabber_lib.dispatch: Unhandled stanza <iq type='error'
id='auth-get-b193ee-0'><error xmlns = 'jabber:client'  code='401' /><query
xmlns = 'jabber:iq:auth'
><username>osad-faea6db6be</username></query></iq>
2009-02-24 15:27:26 jabber_lib._orig_dispatch: <error><conflict xmlns =
'urn:ietf:params:xml:ns:xmpp-streams'  /></error>
2009-02-24 15:30:37 jabber_lib._orig_dispatch: <error><conflict xmlns =
'urn:ietf:params:xml:ns:xmpp-streams'  /></error>
2009-02-24 15:33:36 jabber_lib._orig_dispatch: <error><conflict xmlns =
'urn:ietf:params:xml:ns:xmpp-streams'  /></error>
2009-02-24 15:37:54 jabber_lib._orig_dispatch: <error><conflict xmlns =
'urn:ietf:params:xml:ns:xmpp-streams'  /></error>
2009-02-24 15:41:05 jabber_lib._orig_dispatch: <error><conflict xmlns =
'urn:ietf:params:xml:ns:xmpp-streams'  /></error>
2009-02-24 15:44:48 jabber_lib._orig_dispatch: <error><conflict xmlns =
'urn:ietf:params:xml:ns:xmpp-streams'  /></error>
2009-02-24 15:48:30 jabber_lib._orig_dispatch: <error><conflict xmlns =
'urn:ietf:params:xml:ns:xmpp-streams'  /></error>

All systems here are CentOS 5 (there are some CentOS 4 machines in this
setup, with the same symptoms, but for clarity I ruled them out of these
tests). The proxy updates fine when an event is scheduled for itself (so
the connection between the proxy and the server is not an issue, AFAICS).

Can anyone give me a pointer on how to track this down and solve this?

Regards,

Frans-Jan van Steenbeek