[Spacewalk-list] osa-dispatcher may complain upon startup

[Jan Pazdziora]

Hello,

just for the record: when I star Spacewalk with

	# spacewalk-service start

I get

Starting spacewalk services...
Initializing jabberd processes ...
Starting router: [  OK  ]
Starting sm: [  OK  ]
Starting c2s: [  OK  ]
Starting s2s: [  OK  ]
Starting osa-dispatcher: RHN 19600 2011/08/05 02:56:21 -04:00: ('Server did not return a <features /> stanza',)
RHN 19600 2011/08/05 02:56:21 -04:00: ('Traceback (most recent call last):\n  File "/usr/share/rhn/osad/jabber_lib.py", line 250, in setup_connection\n    c = self._get_jabber_client(js)\n  File "/usr/share/rhn/osad/jabber_lib.py", line 307, in _get_jabber_client\n    c.connect()\n  File "/usr/share/rhn/osad/jabber_lib.py", line 580, in connect\n    raise SSLDisabledError\nSSLDisabledError\n',)
[  OK  ]
Starting tomcat5:                                          [  OK  ]
Waiting for tomcat to be ready ...
Starting httpd: [  OK  ]
Starting Monitoring ...  
[ OK ]
Starting MonitoringScout ...  
[ OK ]
Starting rhn-search...
Starting cobbler daemon: [  OK  ]
Starting RHN Taskomatic...
Done.

This is on 1.5, and I can see the same behvaiour on 1.3 and 1.4.
On 1.2, the error is

Starting osa-dispatcher: RHN 30582 2011/08/05 02:56:13 -04: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 568, 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\nerror: (111, \'Connection refused\')\n',)
[  OK  ]

On all four versions thou, when I then restart osa-dispatcher
as single service, it goes well:

# service osa-dispatcher stop
Shutting down osa-dispatcher: [  OK  ]
# service osa-dispatcher start
[  OK  ] osa-dispatcher: [  OK  ]

So maybe there is some timing issue when jabberd is started right
before osa-dispatcher and it's not ready to fully serve yet?

BTW: I'll accept patches for that double OK during osa-dispatcher
start.

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