A few things to debug this : - enable logging to file for s2s and c2s (in their config files under /etc/jabberd) and check those logfiles for issues - increase debug level of osa-dispatcher in /etc/rhn/rhn.conf (level 4-6 usually is enough to start seeing the errors) - for us things became a lot more stable when we switched the jabberd backend from berkelyDB to sqlite
Hope this helps... -- Jan-Albert Jan-Albert van Ree | Linux System Administrator | MARIN Support Group MARIN | T +31 317 49 35 48 | mailto:j.a.v....@marin.nl | http://www.marin.nl MARIN news: http://www.marin.nl/web/News/News-items/Symposium-Maritime-Design-Forum-1-december-2016.htm -----Original Message----- From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Patrick Sachs Sent: Tuesday, 29 November, 2016 14:32 To: spacewalk-list@redhat.com Subject: [Spacewalk-list] osa-dispatcher still fails with Spacewalk 2.6 hi, i've updated Spacewalk 2.5 to 2.6. and the service osa-dispatcher still fails after a few minutes. System: CentOS 7 osa-dispatcher.log:: 2016/11/29 14:16:45 +02:00 17508 0.0.0.0: osad/jabber_lib.__init__ 2016/11/29 14:16:45 +02:00 17508 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', 'spacew...@teec.de') 2016/11/29 14:20:23 +02:00 17508 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error caught:') not much helpful information :( Any ideas? Patrick _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list