osa-dispatcher encountering connection refused errors when first starting up

Solution Verified - Updated -

Issue

Starting spacewalk services...
Initializing jabberd processes ...
Starting router:                                           [  OK  ]
Starting sm:                                               [  OK  ]
Starting c2s:                                              [  OK  ]
Starting s2s:                                              [  OK  ]
Starting osa-dispatcher: RHN 31458 2011/09/30 09:28:00 +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.4/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\n
error: (111, \'Connection refused\')\n',)
                                                           [  OK  ]
Starting tomcat5:                                          [  OK  ]
Starting httpd:                                            [  OK  ]
Starting Monitoring ...  
[ OK ]
Starting MonitoringScout ...  
[ OK ]
Starting rhn-search...
Starting cobbler daemon:                                   [  OK  ]
Starting RHN Taskomatic...
SERVING!
Done.

Environment

  • Red Hat Network Satellite 5.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content