On 02/15/2010 05:41 PM, James Hogarth wrote:
Monitoring requires oracle connectivity or else it explodes in a big
ball of fiery death - this network requirement is not on the wiki
currently.
Proxy code do not require oracle connectivity, but just oracle client
libraries.
If it dies in "a big ball of fiery death" I would like to see some log.
The ssl-build from /root on the spacewalk server needs to be copied to
the /root of the server to be a proxy or teh configure script fails.
No, it do not require whole copy of /root/ssl-build. It needs just 3(?)
files from that directory (unless you use --force-own-ca) and
installation script will give you exact command how to retrieve it.
If you see some different error, then please report it.
The jabberd configuration had 'secret' for the c2s/sm component
passwords rather than the correct 5259235... etc one and prevented it
from starting till this was fixed.
This one is valid. I filed bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=566124
The jabberd c2s configuration refused to allow SSL to start - had to
copy the c2s.xml file from the spacewalk server over and then amend
the component password and the realm to be correct for the proxy.
This will be the same problem as above. It should be fixed if we use the
same c2s.xsl from spacewalk-jabberd-setup.
--
Miroslav Suchy
Red Hat Satellite Engineering
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
