-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 06 May 2009 16:34:24 +0300 Alexandros Soumplis <[email protected]> wrote:
> Well i have not tried it as i try to stick with documented > procedures. In https://fedorahosted.org/spacewalk/wiki/HowToUpgrade > there is still a paragraph that says: > " > > jabberd-2.2 is known not to work correctly with Spacewalk 0.5 and > RHEL-5 / CentOS-5 and it is highly recommended to disable jabberd and > osa-dispatcher services after Spacewalk upgrade: > > # chkconfig osa-dispatcher off > # chkconfig jabberd off > > " > > Is this not true ? > > > Devan Goodwin wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On Wed, 06 May 2009 16:07:24 +0300 > > Alexandros Soumplis <[email protected]> wrote: > > > > > >> Hi all, > >> > >> Any news regarding spacewalk 0.5 and osad ? Is there any > >> possibility for jabber/osad to work with 0.5 version ? > >> > >> > > > > I thought we had this fixed before 0.5 went out, could you point me > > to the problems you're experiencing and whether or not your install > > was an upgrade? > > > > Thanks, > > > > Devan > > I may have been mistaken and it could still be broken. I will try to find time to do a fresh install soon and see where we stand. If your Spacewalk install was an upgrade from 0.4 to 0.5, would you be willing to try enabling osa-dispatcher and jabberd on your Spacewalk? The errors should be quite apparent, the jabberd service was dying quite quickly after start with errors going to /var/log/messages. Cheers, Devan - -- Devan Goodwin <[email protected]> Software Engineer Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (GNU/Linux) iEYEARECAAYFAkoBm/wACgkQAyHWaPV9my7M1wCeJXD/RV4BdO3aBnHKpq6354EL YNoAoLMN+Npc2n1VhSjyiRrZwWtT1tor =2ajt -----END PGP SIGNATURE----- _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
