[Spacewalk-list] Non-provisioned server registering with spacewalk

[Worsham, Michael]

On the spacewalk server, there are no 'failed' actions. Just 'pending' actions still in progress.

Checked the /var/log/up2date on the client server and found this:

up2date A protocol error occurred: Internal Server Error , attempt #1


-- Michael


-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of m.roth2006 at rcn.com
Sent: Wednesday, April 08, 2009 12:36 PM
To: spacewalk-list at redhat.com
Subject: RE: [Spacewalk-list] Non-provisioned server registering with spacewalk

Michael,

>Date: Wed, 8 Apr 2009 12:00:46 -0400
>From: "Worsham, Michael" <michael.worsham at morris.com>  
>Subject: RE: [Spacewalk-list] Non-provisioned server registering with spacewalk  
>To: Miroslav Suchý <msuchy at redhat.com>
>Cc: spacewalk-list at redhat.com
>
>Okay, I did that and I also did 'yum clean all' just to be sure. 
>
>However, if I go to the server and do 'yum update' it shows that nothing needs to be updated, however the spacewalk server reports that 183 packages needs to be updated. I tried to setup a schedule for the packages, but nothing happens either.

Ok, this is what I've just learned: on the spacewalk server, go to schedule->failed, and select failed systems from that page. There should be info there (hopefully, so you don't have to go through the logs). You can also check /var/log/up2date on the client.

         mark

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