[Spacewalk-list] Best practice for Software channel clean up / removing obsolete packages?

2014-04-15 Thread Götz Reinicke - IT Koordinator
Hi, we use spacewalk for some time and our software channels grew over time. Now we are on Version 2.1 (nice look and feel btw) Furthermore there are a lot of old versions of most software showing up in the different channels in the spacewalk frontend. I remember something, that I

Re: [Spacewalk-list] connection refused with rhnreg_ks

2014-04-15 Thread Michael Mraka
Innes, Duncan wrote: % I was getting the same situation over the weekend, but was running % rhn_register as I hadn't got as far as creating activation keys. % % I'm running Spacewalk 2.1 on Fedora 19 (each fully updated) and created % an empty channel for F19 x86_64. Does this match your

Re: [Spacewalk-list] post-kickstart registration problems after upgrading from 2.0 to 2.1

2014-04-15 Thread Frank Paulick
Hi Bill, i'm facing the same problem. how did you get rid of the problem using spacecmd ? updating in the webgui didn't help me. Regards Frank On 03/05/2014 04:43 PM, Bill Gunter wrote: Ah, thanks for that. I used spacecmd to update all of the profiles and force them to rebuild. Bill --

Re: [Spacewalk-list] Kickstart install with Network config

2014-04-15 Thread Frank Paulick
Hi, i tried the following command: cobbler system add --name=name --interface=eth0 --mac mac --ip-address=ip --subnet=subnet --interface=eth1 --ip-address=2nd ip this only creates /etc/sysconfig/network-scripts/ifcfg-eth1 but not ifcfg-eth0. looking at the mentioned snippet it loosk as if

Re: [Spacewalk-list] post-kickstart registration problems after upgrading from 2.0 to 2.1

2014-04-15 Thread Frank Paulick
Hi, updating in the webgui is working. i just updated the wrong profile. the spacecmd command would be interesting anyway. Regards Frank On 04/15/2014 10:27 AM, Paulick Frank wrote: Hi Bill, i'm facing the same problem. how did you get rid of the problem using spacecmd ? updating in the

[Spacewalk-list] yum install warning

2014-04-15 Thread Dhaval Oza
Dear sir, When I am install below packages on client side, it generate below error. we had configure client with command rhnreg_ks --serverUrl=http://192.168.12.52/XMLRPC --activationkey=key # yum install jabber warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 0608b895:

Re: [Spacewalk-list] Spacewalk client configuration

2014-04-15 Thread Daniel Souvignier
For disabling the repos, use sed -i 's/enabled=1/enabled=0/' /etc/yum.repos.d/*.repo Regards, Daniel Am 15.04.2014 03:11, schrieb Tracy Phillips: Dhaval, Is the server in question automatically registered to the spacewalk server with an activation key? If so, when you try to install via

Re: [Spacewalk-list] yum install warning

2014-04-15 Thread Frank Paulick
Hi, you need to install the rpm key for the package. rpm --import RPM-KEY Regards Frank On 04/15/2014 01:07 PM, Dhaval Oza wrote: Dear sir, When I am install below packages on client side, it generate below error. we had configure client with command rhnreg_ks

Re: [Spacewalk-list] yum install warning

2014-04-15 Thread Gerald Vogt
If you want to use rpms from the EPEL repositories you have to make sure to install the RPM signing key for EPEL-6: rpm --import https://fedoraproject.org/static/0608B895.txt -Gerald On 15.04.2014 13:07, Dhaval Oza wrote: Dear sir, When I am install below packages on client side, it

Re: [Spacewalk-list] yum install warning

2014-04-15 Thread Dhaval Oza
Dear Gerald Please note that: we do not have internet access on client machine , so please let me know how to configure for the same on client side . It will be grateful if any one can help us in solving the issue. Thanks and Regards, Dhaval Oza. On 04/15/2014 04:47 PM, Gerald Vogt wrote:

Re: [Spacewalk-list] yum install warning

2014-04-15 Thread Gerald Vogt
Download the key, save it to a USB stick, and install it on the client. -Gerald On 15.04.2014 13:35, Dhaval Oza wrote: Dear Gerald Please note that: we do not have internet access on client machine , so please let me know how to configure for the same on client side . It will be

Re: [Spacewalk-list] yum install warning

2014-04-15 Thread Stuart Green
Or SFTP over your LAN? Don't think you'll get a Elegant solution for this one I'm afraid! Download the key, save it to a USB stick, and install it on the client. -Gerald On 15.04.2014 13:35, Dhaval Oza wrote: Dear Gerald Please note that: we do not have internet access on client machine ,

Re: [Spacewalk-list] yum install warning

2014-04-15 Thread Gerald Vogt
Are you sure you know what you are doing? You have to install the RPM key RPM key on the client. If you don't know how to transfer something to the client, I guess noone here can help you. -Gerald On 15.04.2014 13:58, Dhaval Oza wrote: Dear Gerald Our server is at remote place ,it's not

Re: [Spacewalk-list] connection refused with rhnreg_ks

2014-04-15 Thread Innes, Duncan
Michael, This worked a treat. Got me on to my next issue at least. Thanks Duncan -Original Message- From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Michael Mraka Sent: 15 April 2014 08:40 To: spacewalk-list@redhat.com Subject: Re:

Re: [Spacewalk-list] Best practice for Software channel clean up / removing obsolete packages?

2014-04-15 Thread Dimitri Yioulos
On Tue, 15 Apr 2014 09:18:49 +0200, Götz Reinicke - IT Koordinator wrote Hi, we use spacewalk for some time and our software channels grew over time. Now we are on Version 2.1 (nice look and feel btw) Furthermore there are a lot of old versions of most software showing up in the

Re: [Spacewalk-list] Best practice for Software channel clean up / removing obsolete packages?

2014-04-15 Thread Götz Reinicke - IT Koordinator
Am 15.04.14 15:22, schrieb Dimitri Yioulos: On Tue, 15 Apr 2014 09:18:49 +0200, Götz Reinicke - IT Koordinator wrote Hi, we use spacewalk for some time and our software channels grew over time. Now we are on Version 2.1 (nice look and feel btw) Furthermore there are a lot of old versions

Re: [Spacewalk-list] Kickstart install with Network config

2014-04-15 Thread Frank Paulick
Hi, to get multiple nics configured with cobbler and configured during kickstart installation the following steps are required: cobbler system add --name=system name first NIC Config cobbler system edit --name=system name second NIC Config The 2nd command has to be issued for every NIC to be

Re: [Spacewalk-list] Best practice for Software channel clean up / removing obsolete packages?

2014-04-15 Thread Dimitri Yioulos
On Tue, 15 Apr 2014 17:06:33 +0200, Götz Reinicke - IT Koordinator wrote Am 15.04.14 15:22, schrieb Dimitri Yioulos: On Tue, 15 Apr 2014 09:18:49 +0200, Götz Reinicke - IT Koordinator wrote Hi, we use spacewalk for some time and our software channels grew over time. Now we are on

Re: [Spacewalk-list] Best practice for Software channel clean up / removing obsolete packages?

2014-04-15 Thread Dimitri Yioulos
On Tue, 15 Apr 2014 11:28:34 -0400, Dimitri Yioulos wrote On Tue, 15 Apr 2014 17:06:33 +0200, Götz Reinicke - IT Koordinator wrote Am 15.04.14 15:22, schrieb Dimitri Yioulos: On Tue, 15 Apr 2014 09:18:49 +0200, Götz Reinicke - IT Koordinator wrote Hi, we use spacewalk for some time

Re: [Spacewalk-list] Installing Spacewalk on CentOS 6.5

2014-04-15 Thread Tracy Phillips
Gajan, What version of Spacewalk are you trying to install and what repos have you enabled to pull from? Tracy Phillips Weberize, Inc. On Mon, Apr 14, 2014 at 9:45 PM, Kugamoorthy Gajananan ga...@jp.ibm.comwrote: Hi, I am trying to install spacewalk on CentOS 6.5 as described here :

[Spacewalk-list] Auto subscribe to Probe Suites?

2014-04-15 Thread Tracy Phillips
Hello, Is it possible to subscribe to Probe Suites automatically during kickstart using Activation Keys, Groups... or something? Tracy Phillips ___ Spacewalk-list mailing list Spacewalk-list@redhat.com

Re: [Spacewalk-list] Installing Spacewalk on CentOS 6.5

2014-04-15 Thread Kugamoorthy Gajananan
Hi Phillips, Thank you for your reply. To answer questions: rpm -Uvh http://yum.spacewalkproject.org/2.1/RHEL/6/x86_64/spacewalk-repo-2.1-2.el6.noarch.rpm rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm Meantime, I resolved the issue by doing the following