[Spacewalk-list] osa-dispatcher not starting
Daryl Rose
darylrose at outlook.com
Fri Jul 14 14:09:39 UTC 2017
Looks like the osa-dispatcher has not been running since June 15th. The osa-dispatcher.log simply has this error:
2017/06/15 09:40:11 -05:00 5494 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error caught:')
2017/07/13 15:30:51 -05:00 33224 0.0.0.0: osad/jabber_lib.__init__
2017/07/13 15:30:51 -05:00 33224 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', '<FQDN SW Server>')
2017/07/13 15:30:51 -05:00 33224 0.0.0.0: osad/osa_dispatcher.fix_connection('Upstream notification server started on port', 1290)
2017/07/13 15:30:51 -05:00 33224 0.0.0.0: osad/jabber_lib.process_forever
2017/07/13 15:30:51 -05:00 33224 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error caught:')
2017/07/13 15:30:53 -05:00 33251 0.0.0.0: osad/jabber_lib.__init__
2017/07/13 15:30:53 -05:00 33251 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', '<FQDN SW Server>')
2017/07/13 15:30:53 -05:00 33251 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error caught:')
To the best of my knowledge, nothing on the SW server has changed. I had problems with the proxy, which I had to rebuild, but nothing on the SW server itself has changed.
Where do I need to start looking?
Thanks
Daryl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20170714/9a862285/attachment.htm>
More information about the Spacewalk-list
mailing list