Do you mean the last sync time? There isn't one since there's a CLI script
that does it, modified from the docs on syncing rpmforge/epel.
The taskomaticd is running if that's the one you mean
There are a few older errors "Error com.redhat.rhn.taskomatic.task.RepoSyncTask
- Content Source could
I'm trying to track down why tasks are no longer executing on my
Spacewalk server (1.0, running on RHEL5). I discovered that there was a
bogus entry in the RhnTaskQueue table - it had a null value in the
task_data field. Each time taskomatic started up it immediately threw
an exception and st
I call custom API scripts in the %post script to deal with this.
in a 'am i registered, if so delete me' then 'register system' kind of way?
would you mind sharing that snippet?
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://
On 10 May 2010 15:52, Tom Brown wrote:
>
>>>
>>>
>>
>> Is this with Spacewalk 1.0 or are you using an earlier version?
>>
>> Reason for asking is that we're contemplating upgrading from 0.8 to 1.0
>> and are wondering if we should keep the old cobbler (1.6.6) or if 1.0
>> actually works with cobbl
Is this with Spacewalk 1.0 or are you using an earlier version?
Reason for asking is that we're contemplating upgrading from 0.8 to
1.0 and are wondering if we should keep the old cobbler (1.6.6) or if
1.0 actually works with cobbler 2.
spacewalk relies on cobbler not cobbler > 2.x
On 10/05/10 16:29, James Hogarth wrote:
Hi all,
A quick heads up
My spacewalk server was updated to cobbler-2.0.3 when EPEL updated to
that from 1.6.6.
Looks like something borked in the api spacewalk liases with on
upgrade (or version) as my kickstarts had snippets in them that had
not be
Hello.
I have the same problem. I replaced the $variable of my snippet by \$variable
and its work. But I have others litle problem to solve yet.
-Message d'origine-
De : spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] De la part de James Hogarth
Envoyé : lun
Hi all,
A quick heads up
My spacewalk server was updated to cobbler-2.0.3 when EPEL updated to
that from 1.6.6.
Looks like something borked in the api spacewalk liases with on
upgrade (or version) as my kickstarts had snippets in them that had
not be expanded when viewing the kickstarts. not
I call custom API scripts in the %post script to deal with this.
On Mon, May 10, 2010 at 9:46 PM, Tom Brown wrote:
>
>>
>> I want to reduce the manual work to do when reinstalling a system and
>> therefore avoid duplicates in my spacewalk installation.
>>
>> The only way to do that is to generate
I want to reduce the manual work to do when reinstalling a system and
therefore avoid duplicates in my spacewalk installation.
The only way to do that is to generate a reactivation key for each
system. As far as I found out this can only be done by using the web
interface manually.
Is there a
Hi,
I want to reduce the manual work to do when reinstalling a system and
therefore avoid duplicates in my spacewalk installation.
The only way to do that is to generate a reactivation key for each
system. As far as I found out this can only be done by using the web
interface manually.
Is there
Joseph Lundgren wrote:
% Greeting wonderful Spacewalk developers!
%
% Do you have any plans to release a Spacewalk 1.0 client for RHEL 4.8?
Hi Joseph,
in the past we've never released client tools for RHEL 4.
On the other hand you should be able to setup RHEL 4 as a Spacewalk
client using stock
Daniel Wittenberg wrote:
% Anyone else using custom repos? I have one setup for RPMForge
% according to the example spacewalk docs, and it does the same thing.
% There is nothing in /var/cache/rhn/repodata/, except for the
% Base OS and the Updates channel. I create the links but then still
% can
- "rob morrien" wrote:
> hello to all,
>
> i upgraded spacewalk from 0.8 to 1.0 version.
>
> i used the command :
>
> /usr/bin/spacewalk-repo-sync --channel spacewalk-client-i386 \
> --url
> http://spacewalk.redhat.com/yum/1.0-client/RHEL/5/i386/
> \
>
14 matches
Mail list logo
