David,
Thanks for posting your configs, by using them as a base for mine, and heeding
the advice to remove the osad-auth.conf file as mentioned in
https://bugzilla.redhat.com/show_bug.cgi?id=590608 I was able to get osad back.
Much appriciated,
Dave
-Original Message-
From: spacewalk-
I seem to be suffering from a similar issue after a 1.1 -> 1.2 upgrade.
The OSAD / Jabber issue is present, but I don’t get any 500 errors on the
webapp. I do remember on my initial (1.1) setup I had the same error. I had to
modify an SSL related setting regarding jabber, but it seems to be miss
I dont see why it wouldnt be possible. I have a similar setup except
using an Oracle Enterprise Linux yum server that pulls the updates,
which is sync'd to the Spacewalk server. The only issue i've had has
been the yum repo and spacewalk pulling packages at the same time that
made for some broken
