[Spacewalk-list] cobbler-sync and kickstartfile-sync

[Hagberg, Keith]

What could be causing cobbler to be unavailable. 

When I run top cobblerd is usually the top consumer of cpu. It normally is taking 100% of one cpu. 

Keith

-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Tomas Lestach
Sent: Monday, October 03, 2011 4:47 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] cobbler-sync and kickstartfile-sync

Hello,

this e-mails come from taskomatic. This is the only way, how to notify 
the user something went wrong.
I suppose that you got also an e-mail notifying you that the mentioned 
tasks failed. Notices about tasks coming back to normal are sent only 
after a failure.
kickstartfile-sync and cobbler-sync usually fail when cobbler isn't 
available. So, I'd recommend to check cobbler.

Tomas
--
Tomas Lestach
RHN Satellite Engineering, Red Hat


On 09/30/2011 08:56 PM, Hagberg, Keith wrote:
> Getting lots of the following
>
> Taskomatic bunch kickstartfile-sync-bunch was scheduled to run within
> the kickstartfile-sync-default schedule.
>
> Subtask kickstartfile-sync finished successfuly and is back to normal.
>
> And
>
> Taskomatic bunch cobbler-sync-bunch was scheduled to run within the
> cobbler-sync-default schedule.
>
> Subtask cobbler-sync finished successfuly and is back to normal.
>
> We are also seeing a lot or error 500's when trying to register systems.
>
> Any idea how to remediate this.
>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list