Odd that everything seems to be working well, except when I schedule a package
to be updated it goes ok with no errors, I see lots of communication (with
wireshark) between spacewalk and the server being updated, and then spacewalk
says completed successfully, yet the package I pushed isn't actu
If I do:
/etc/init.d/osad start
Starting osad: Traceback (most recent call last):
File "/usr/share/rhn/osad/jabber_lib.py", line 254, in setup_connection
c = self._get_jabber_client(js)
File "/usr/share/rhn/osad/jabber_lib.py", line 311, in _get_jabber_client
c.connect()
File "/usr/s
I must be missing something, but here's what I need to do:
I need to be able to register a client with Spacewalk, assign it to a group, and have a set of packages assigned to the
group. For example, let's say I want all members of "Group A" to get the alpine rpm. So, assume I then register a n
Hi all,
Just a quick heads up until I get in the office tomorrow and can pull
some logs to get a better picture but putting it out there now in case
anyone sees similar
Since upgrading to spacewalk 1.0 it has become a much more common
occurrence to find clients on the far side of the spacewal
On 17 May 2010 10:30, James Hogarth wrote:
> Hi all,
>
> I figure someone else has probably run across this and can provide some
> advice.
>
> After enabling online backups last week on our oracle-xe instance we
> hit a problem of the flash recovery area filling up and stopping
> oracle (and henc
On 20 May 2010 13:15, Marcus Moeller wrote:
> Hi.
>
>> I've managed to set my test system to boot by PXE and register on spacewalk
>> server, everything went as expected except for the package sync.
>> On the event history I get the following event:
>>
>> Schedule a package sync for kickstarts sch
Hi.
> I've managed to set my test system to boot by PXE and register on spacewalk
> server, everything went as expected except for the package sync.
> On the event history I get the following event:
>
> Schedule a package sync for kickstarts scheduled by (none)
> Details:
> This action's status is
On 20 May 2010 09:50, Milan Zazrivec wrote:
> On Wednesday 19 May 2010 23:32:06 James Hogarth wrote:
>> KVM host is fully updated Centos 5.5
>>
>> Spacewalk instance is a fully updated spacewalk 1.0 (with cobbler
>> 1.6.6 not 2.0.3) on centos 5.5 with epel.
>>
>> On an attempt at a remote provisio
On Wednesday 19 May 2010 23:32:06 James Hogarth wrote:
> KVM host is fully updated Centos 5.5
>
> Spacewalk instance is a fully updated spacewalk 1.0 (with cobbler
> 1.6.6 not 2.0.3) on centos 5.5 with epel.
>
> On an attempt at a remote provisioning I get:
>
> libvirtd (pid 4266) is running...
Hello,
> xmlrpclib.Fault: have permissions to perform this action.'>
the user my installation is using got no roles but is associated with a
system group which consists of all systems that are registered on the
spacewalk server.
How are the rights on your installation set?
Which spacewalk versi
10 matches
Mail list logo
