I actually did a little hack with a case statement in /etc/sysconfig/jabberd where ir dlete the database prior ot the start and it practically speaking solved my problem; however from what I've seen in the jabberd changelogs it looks like the root cause is a known issue with berkly db files in jabberd which has been fixed in newer versions. Interestingly I've heard anecdotally if you configure jabber in a clustered mode with PostgreSQL as a back end this is a non-issue which would be useful for an load balanced HA configuration Sent from my BlackBerry 10 smartphone.
Check for errors in the /var/log/rhn/rhn_server_xmlrpc.log logfile. The client's OSAD credentials may not be good anymore. You can try this: On the client system, run: # service osad stop ; rm -f /etc/sysconfig/rhn/osad-auth.conf ; service osad start Worst case scenario, you need to rebuild the jabberd database on the Spacewalk server. This can be safely done by doing the following on the Spacewalk server: # service jabberd stop ; rm -Rf /var/lib/jabberd/db/* ; service jabberd start The following document covers a lot of the common OSAD\Jabber issues On Sat, Jan 17, 2015 at 8:53 PM, Dewangga Bachrul Alam <dewangg...@xtremenitro.org> wrote: Hi, | ||
_______________________________________________ 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
