[Spacewalk-list] After Spacewalk serverrename/selfsigned SSL-issues on yum-updates for CentOS

2013-06-13 Thread Jonathan Hoser
Dear all, once again I'm puzzling about some strange issue and am hoping for some valued input I experienced in the past on this list: The gist (for the hasty reader:): CentOS yum/curl rejects my Spacewalk' servers certificate as Bad certificate received while a check with openssl s_client

Re: [Spacewalk-list] Keepalive for Database Connections?

2013-06-13 Thread Stefan Lasche
Hi Stefan, you can create /etc/tnsname.ora with connect string you need. Then just change db_name in /etc/rhn/rhn.conf to the tnsname you've created (instead of default //host:port/name) and that's it :). Thanks a lot Michael! That did the trick. The file is actually called

Re: [Spacewalk-list] Keepalive for Database Connections?

2013-06-13 Thread Michael Mraka
Stefan Lasche wrote: % Hi Stefan, % % you can create /etc/tnsname.ora with connect string you need. % Then just change db_name in /etc/rhn/rhn.conf to the tnsname you've created % (instead of default //host:port/name) and that's it :). % % % Thanks a lot Michael! That did the trick. The

Re: [Spacewalk-list] libxml2-python and kickstart

2013-06-13 Thread Paul Robert Marino
One thing I found is that you need to use the image files from the Everything install disk when creating the kickstart distribution or you will run into problems like the one you described with the update channel. On Mon, Jun 10, 2013 at 8:08 AM, Jan Hutaƙ jhu...@redhat.com wrote: On Mon, 3

Re: [Spacewalk-list] libxml2-python and kickstart

2013-06-13 Thread Ian Forde
(To Jan) Question. Given that this is discussed in http://bugs.centos.org/view.php?id=4978 (going back almost 2 years now), and is still an active issue, I'm wondering if the official answer is to not use the updates repo during installation or not. But if this is just a metadata bug, as