Bit more info. I cranked the debugging up to 5 and am seeing this:
2011/01/05 10:07:02 -04:00 10877 0.0.0.0: osad/jabber_lib.connect('Connected',)
2011/01/05 10:07:02 -04:00 10877 0.0.0.0: osad/jabber_lib.connect('Expecting
features stanza, got:', <features><address xmlns =
'http://affinix.com/jabber/address' >10.9.103.69</address><auth xmlns =
'http://jabber.org/features/iq-auth' /><register xmlns =
'http://jabber.org/features/iq-register' /><starttls xmlns =
'urn:ietf:params:xml:ns:xmpp-tls' ><required /></starttls></features>)
I don't know what that means though. My guess is that osa-dispatcher is not
talking correctly to jabberd?
On Jan 5, 2011, at 9:55 AM, Wojtak, Greg wrote:
> We recently did an install of Spacewalk 1.1. We are having some trouble with
> osa-dispatcher, however. Everything starts OK, but every 5 minutes, on the
> spacewalk server, we get
>
> 2010/12/30 10:30:02 -04:00 13104 0.0.0.0:
> rhnSQL/driver_cx_Oracle.connect('Connecting to database', 'xe')
> 2010/12/30 10:30:02 -04:00 13104 0.0.0.0:
> osad/jabber_lib._get_jabber_client('Connecting to', '<spacewalk-host>')
> 2010/12/30 10:30:02 -04:00 13104 0.0.0.0: osad/jabber_lib.__init__
> 2010/12/30 10:30:02 -04:00 13104 0.0.0.0: osad/jabber_lib.connect
> 2010/12/30 10:30:02 -04:00 13104 0.0.0.0:
> osad/jabber_lib.setup_connection('Connected to jabber server',
> '<spacewalk-host>')
> 2010/12/30 10:30:02 -04:00 13104 0.0.0.0: osad/dispatcher_client.start
> 2010/12/30 10:30:02 -04:00 13104 0.0.0.0:
> osad/jabber_lib.auth('rhn-dispatcher-sat', 'rhn-dispatcher-c23965',
> 'superclient', 1)
> 2010/12/30 10:35:02 -04:00 13104 0.0.0.0: osad/jabber_lib.main('ERROR',
> 'Error caught:')
> 2010/12/30 10:35:02 -04:00 13104 0.0.0.0: osad/jabber_lib.main('ERROR',
> 'Traceback (most recent call last):\n File
> "/usr/share/rhn/osad/jabber_lib.py", line 120, in main\n c =
> self.setup_connection(no_fork=no_fork)\n File
> "/usr/share/rhn/osad/jabber_lib.py", line 288, in setup_connection\n
> resource=self._resource)\n File "/usr/share/rhn/osad/dispatcher_client.py",
> line 33, in start\n self.auth(username, password, resource)\n File
> "/usr/share/rhn/osad/jabber_lib.py", line 886, in auth\n
> self.SendAndWaitForResponse(auth_set_iq)\n File
> "/usr/lib/python2.4/site-packages/jabber/jabber.py", line 401, in
> SendAndWaitForResponse\n return self.waitForResponse(ID,timeout)\n File
> "/usr/share/rhn/osad/jabber_lib.py", line 1154, in waitForResponse\n raise
> TimeoutError()\nTimeoutError\n')
> 2010/12/30 10:35:12 -04:00 13104 0.0.0.0:
> osad/jabber_lib._get_jabber_client('Connecting to', '<spacewalk-host>')
>
>
> I've got the debugging for osa-dispatcher set to 2. I can easily set it
> higher if needed, but really, I'm at a loss as to where to start with
> debugging this. The clients appear to be running fine, but their status
> never gets updated in the UI, even after an OSA ping is initiated.
>
> Can someone help get me pointed in the right direction?
>
> Thanks!
>
> Greg
>
> _______________________________________________
> Spacewalk-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
