Hi,
I have the rhel5.3 i386 kickstart working perfectly, packages get
installed, all gpg keys go in automatically, osad works and everything
is pretty much groovy.
Then I created the 64-bit channels and the ks distribution, cloned the
ks profile from the i386 and just changed the base channe
Jeff,
Thanks very much for the feedback, I tried your suggestions,but I
still get the same error message, even after the upgrade.
Any one else having this issue or issues with the graphs?
2009-08-27 09:39:29,655 [TP-Processor6] ERROR
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].
After further experimentation,
All that is needed is:
Change the servername in /etc/sysconfig/rhn/up2date
Register to the appropriate channel
RHEL 3 clients are now being updated by the internal Spacewalk server
-Original Message-
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk
Just got this to work...
Have only done it this once, so when I solidify the process, I will reply with
details.
Rich
-Original Message-
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Gomes, Rich
Sent: Wednesday, August 26, 2009 11:55 AM
Randy Rubins wrote:
> What process on the Spacewalk server generates the kickstart profile
> .cfg file in /var/lib/rhn/kickstarts/wizard directory?
> Is there a way to update the template(s) used by this process, like one
> would normally be able to do via standard cobbler interface/templates?
>
>
What process on the Spacewalk server generates the kickstart profile .cfg file
in /var/lib/rhn/kickstarts/wizard directory?
Is there a way to update the template(s) used by this process, like one would
normally be able to do via standard cobbler interface/templates?
Maybe someone could also expa
Could I just use yum from say Dags and then create point to the repo on the
spacewalk server?
What is the standard path?
-Original Message-
From: Miroslav Suchý [mailto:msu...@redhat.com]
Sent: Friday, August 21, 2009 11:27 AM
To: spacewalk-list@redhat.com; Gomes, Rich
Subject: Re: [Spac
Hi,
The upgrade fixed some nasty issues for us at work.
But I got a new one (I think): when I click on a system and on the
packaes which can be upgraded, I see the kernel stated multiple times:
kernel-2.6.9-89.0.9.EL kernel-2.6.9-78.0.22.EL
kernel-2.6.9-89.0.9.EL
On Wed, Aug 26, 2009 at 12:01:33AM +0200, Michiel van Es wrote:
>
> I used the steps you told me and that worked!
> Thanks a bunch! :)
> When I go to the upgrade package step and run the semanage commando I get:
>
>
> [r...@devmx01 ~]# semanage port -d -t cobbler_port_t -p tcp 25152
> /usr/sbin/
