[Spacewalk-list] osa-dispatcher problems. no system ever reports

Joshua Roys joshua.roys at gtri.gatech.edu
Mon Feb 8 13:01:24 UTC 2010


On 02/08/2010 07:13 AM, Stefan Bluhm wrote:
> Stopping s2s: [FAILED]
>

This means it wasn't running, which is bad - see below.

> RHN 7447 2010/02/08 12:00:55 +02:00: ('Traceback (most recent call
> last):\n File "/usr/share/rhn/osad/jabber_lib.py", line 254, in
> setup_connection\n c = self._get_jabber_client(js)\n File
> "/usr/share/rhn/osad/jabber_lib.py", line 311, in _get_jabber_client\n
> c.connect()\n File "/usr/share/rhn/osad/jabber_lib.py", line 577, in
> connect\n jabber.Client.connect(self)\n File
> "/usr/lib/python2.6/site-packages/jabber/xmlstream.py", line 464, in
> connect\n else: self._sock.connect((self._hostIP, self._port))\n File
> "<string>", line 1, in connect\nerror: [Errno 111] Connection refused\n',)
>

That "Connection refused" was caused by the first issue - so let's debug 
jabberd.  Do you have any logs in /var/log/messages (or wherever you've 
configured jabberd logs to go)?

Josh

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2719 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20100208/d67e4e84/attachment.p7s>


More information about the Spacewalk-list mailing list