I've seen lots of information on migrating to a database other than
oracle-xe and such and they work just fine. I've tested them myself
and I was happy with the results however, what I'd really like to be
able to do is do an install directly to an existing oracle db.
When I try to run spacewalk-se
After installing the virt package, did you run 'rhn-profile-sync'?
CC
On Tue, Sep 14, 2010 at 2:04 AM, Balazs Zachar wrote:
> On 09/13/2010 10:20 AM, Michael Mraka wrote:
>>
>> Balazs Zachar wrote:
>> % Hi List,
>> %
>> % My configuration:
>> % 1. Management server:
>> % - physical server
>> % -
On 09/13/10 11:51, Stroehmann, James wrote:
My clients auto-register when kickstarting, you might be missing the spacewalk
client tools in your package list?
Also, one problem i was having originally was that new systems would not have
the correct time on them, so i have a script in my kick
On 09/13/2010 10:20 AM, Michael Mraka wrote:
Balazs Zachar wrote:
% Hi List,
%
% My configuration:
% 1. Management server:
% - physical server
% - CentOS 5.5
%
% 1. Spacewalk server:
% - kvm virt machine on the management server
% - CentOS 5.5
% - spacewalk 1.1
% - Oracle Xe
%
% I have registered
On 09/13/10 11:51, Stroehmann, James wrote:
My clients auto-register when kickstarting, you might be missing the spacewalk
client tools in your package list?
Also, one problem i was having originally was that new systems would not have
the correct time on them, so i have a script in my kick
My clients auto-register when kickstarting, you might be missing the spacewalk
client tools in your package list?
Also, one problem i was having originally was that new systems would not have
the correct time on them, so i have a script in my kickstart to use rdate to
update them.
look in t
ok thanks, I was thinking thats what I had to do, but I was was hoping there
would be something more elegant and
built-in.
Jason
On Mon, Sep 13, 2010 at
10:28:19AM -0500, Mike Hanby
wrote:
> This may not be the spacewalk way, but in my kickstart files I have the
> clients register via:
>
>
This may not be the spacewalk way, but in my kickstart files I have the clients
register via:
/usr/sbin/rhnreg_ks --serverUrl=http://spacewalk.some.domain/XMLRPC \
--activationkey=1-x
Where the activation key is the appropriate one for whichever channel the
client needs to join.
I
I noticed that my clients after kickstarting are not
registered with the spacewalk server by default, is there a way to make
kickstarted systems register with the
spacewalk server by default so that after they're kickstarted, I can just do a
"yum install screen" or whatever?
regards,
Jason
O
> On Mon, Sep 13, 2010 at 01:50:41PM +0200, rob morrien wrote:
>> hello to all,
>>
>>
>> i try to reposync the spacewalk.repo 1.1 , it looks like that
>> there are problems in the repo locations of the satelite repo server.
>>
>> see below the output of repo sync
>>
>> regsrd rob
>>
>>
>>
>> Repo
On Mon, Sep 13, 2010 at 01:50:41PM +0200, rob morrien wrote:
> hello to all,
>
>
> i try to reposync the spacewalk.repo 1.1 , it looks like that
> there are problems in the repo locations of the satelite repo server.
>
> see below the output of repo sync
>
> regsrd rob
>
>
>
> Repo http://s
Hi,
I think it is not a problem of the spacewalk repo but a "problem" of hte
reposync as I got the same error for the centos base 5 repo for 2 times.
Regards,
Balazs
On 09/13/2010 01:50 PM, rob morrien wrote:
hello to all,
i try to reposync the spacewalk.repo 1.1 , it looks like that
there
hello to all,
i try to reposync the spacewalk.repo 1.1 , it looks like that
there are problems in the repo locations of the satelite repo server.
see below the output of repo sync
regsrd rob
Repo http://spacewalk.redhat.com/yum/1.1/RHEL/5/i386/ has 235 packages.
1/235 : spacewalk-backend-sq
Just to follow up - I just hocked version 1.0 into my test lab and rollback
seems to work just fine, so this only appears to be an issue with version 1.1
so far. I then took one of my other environments and threw on the
nightly-updates repo to bring it up to 1.2, but still hit the same issue, s
Balazs Zachar wrote:
% Hi List,
%
% My configuration:
% 1. Management server:
% - physical server
% - CentOS 5.5
%
% 1. Spacewalk server:
% - kvm virt machine on the management server
% - CentOS 5.5
% - spacewalk 1.1
% - Oracle Xe
%
% I have registered both servers into the spacewalk, but I can
I've recently performed fresh installs of Spacewalk 1.1 using the installation
guide on the official Wiki page across three separate environments - in all
cases however I've had no luck making use of the rollback functions (performed
repetitively as I'm relatively new to Spacewalk and first assu
Götz Reinicke - IT-Koordinator wrote:
% Hi,
%
% some time ago I set up spacewalk 1.0 and added a couple of i386 and
% x86_64 servers. Everything seams fine so far and working.
%
% Today I noticed, that some updates are availabel for the servers I manage.
%
% But in the 'Spacewalk System Overview
Thank you.
Now it is working.
I'll run these commands nightly too.
2010/9/13 Marco Giunta
> Hi,
> try to stop jabberd and osad service:
>
> /sbin/service jabberd stop
> /sbin/service osa-dispatcher stop
>
> remove jabberd auth db:
>
> rm -Rf /var/lib/jabberd/db/*
>
> and start again services,
Hi,
some time ago I set up spacewalk 1.0 and added a couple of i386 and
x86_64 servers. Everything seams fine so far and working.
Today I noticed, that some updates are availabel for the servers I manage.
But in the 'Spacewalk System Overview' the updates don't show up, for
the servers there are
19 matches
Mail list logo
