[Spacewalk-list] osa-dispatcher not running or not connecting

[Jan Pazdziora]

On Fri, Jul 08, 2011 at 05:04:06PM +0200, Andre van der Vlies wrote:
> Problems after 1.2 -> 1.4 upgrade...
> 
> Hi,
> I decided to make a fresh start, cleaned out all but the oracle stuff...
> 
> It all seemed to install okay...
> But now my osa-dispatcher is not running or does not allow connecting to.
> 
> I've found a 2009 thread with a fix
> (http://www.mail-archive.com/spacewalk-list@redhat.com/msg02909.html). I
> didn't help however.
> 
> I'm not sure what logs to send...
> 
> My 'osad.log' is filled with:
>     2011-07-08 16:18:36 jabber_lib.main:
>         Unable to connect to jabber servers, sleeping 92 seconds
> 
> /var/log/messages:
>  Jul  8 16:56:07 zwalk jabberd/sm[11090]: zwalk.henz.nl ready for sessions
> Jul  8 16:56:18 zwalk jabberd/c2s[11097]: [7] [94.232.160.136, port=39382]
> connect
> Jul  8 16:56:18 zwalk jabberd/c2s[11097]: [7] legacy authentication
> succeeded: host=, username=rhn-dispatcher-sat, resource=superclient, TLS
> negotiated
> Jul  8 16:56:18 zwalk jabberd/c2s[11097]: [7] requesting session:
> jid=rhn-dispatcher-sat at zwalk.henz.nl/superclient
> Jul  8 16:56:18 zwalk jabberd/sm[11090]: session started:
> jid=rhn-dispatcher-sat at zwalk.henz.nl/superclient
> 
> [root at zwalk log]# tail -f messages | grep -e jabber -e osad
> Jul  8 16:57:28 zwalk jabberd/c2s[11097]: [11] [94.232.160.136,
> port=52536] connect
> Jul  8 16:57:28 zwalk jabberd/c2s[11097]: [11] legacy authentication
> succeeded: host=, username=osad-9f31af9ccb, resource=osad, TLS negotiated
> Jul  8 16:57:28 zwalk jabberd/c2s[11097]: [11] requesting session:
> jid=osad-9f31af9ccb at zwalk.henz.nl/osad
> Jul  8 16:57:28 zwalk jabberd/sm[11090]: session started:
> jid=osad-9f31af9ccb at zwalk.henz.nl/osad
> 
> 
> a telnet to port 5222 works. I' am talking localhost only (yet)....

Actually, the

	Unable to connect to jabber servers

is printed when exception JabberConnectionError is raised in the
osad/jabber_lib code, and that seems to happen when the XMLRPC
communication with the server does not go well.

So you might want to check /var/log/up2date on the client, or the
XMLRPC logs on the server.

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat