I just did an upgrade to spacewalk 1.2 on both the server and the client. The client's OSA Status is still showing up as 'offline as of unknown' in the web UI, but all of the errors about not being able to connect have stopped being logged. I increased the debugging some more and it looks like osa-dispatcher is happily talking to jabberd. Still no clue as to why the client is showing offline though. Anything else I can try?
Thanks! Greg On Jan 5, 2011, at 10:47 AM, Jan Pazdziora wrote: > On Wed, Jan 05, 2011 at 04:36:27PM +0100, David Hrbáč wrote: >> Dne 5.1.2011 16:13, Jan Pazdziora napsal(a): >>> On Wed, Jan 05, 2011 at 09:55:12AM -0500, Wojtak, Greg wrote: >>>> We recently did an install of Spacewalk 1.1. We are having some trouble >>>> with osa-dispatcher, however. Everything starts OK, but every 5 minutes, >>>> on the spacewalk server, we get >>> >>> The latest Spacewalk release is 1.2. We have fixed multiple issues >>> around osa-dispatcher. Also, Spacewalk 1.2 has the correct jabberd >>> configuration for the latest jabberds (2.2). I'd say upgrade to >>> Spacewalk 1.2 is your best bet moving forward. >> >> Jan, >> osa-dispatcher and jabber communication in SW1.2 is not working. I have >> reported it in BZ without any reply. > > If you have bug 662593 in mind, that's however different issue. What > Greg reports is error during osa-dispatcher connect to jabberd. Which > I've pushed updated packages for on December 9th, 2010. > > -- > Jan Pazdziora > Principal Software Engineer, Satellite Engineering, Red Hat > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
