Hi Matt,
   I'm not sure I have anything helpful for you, but I'm particularly 
interested in problem 1. I've been getting similar issues. One question I have 
for you is whether you've included gpg keys for Spacewalk-2010 and  EPEL in 
your kickstart file.  Without these keys, I think some post-install package 
installs will fail, which may be part of the puzzle.  
   Anyway, if you make any progress, I'd be grateful if you'd let me know.
                                                        -Phil

On May 31, 2011, at 7:06 AM, Matthew Darcy wrote:

>  
> >Problem 1.) I think this is the root a few of the problems. I kickstart a 
> >machine, it as an activation key that >subscribes it to 4 software channels 
> >and 4 config channels. The kickstart process finishes and the client 
> >reboots, >in the spacewalk web interface I can see the machine as a 
> >registered client. I can see it subscribed to the 4 >software channels 
> >correctly in the web interface, it's entitlemtns are management, monitoring 
> >and provisioning, in >the configuration menu, I can see it's subscribed to 
> >the correct for config channels. The issue is that none of the 4 >config 
> >channels have deployed the files. If I do a "rhn_check" on the client, I get 
> >the following error
>  
> [>quote]
> >[root@vmbuild01 ~]# rhn_check
> >Package rhncfg-5.9.52-1.el5.noarch already installed and latest version
> >Package rhncfg-actions-5.9.52-1.el5.noarch already installed and latest 
> >version
> >Package rhncfg-client-5.9.52-1.el5.noarch already installed and latest 
> >version
> >XMLRPC ProtocolError: <ProtocolError for spacewalk01.sccis.net /XMLRPC: 500 
> >Internal Server Error>
> >[/quote]
>  
> >the spacewalk server is reachable, I can see the client in the webui, I can 
> >search the repos on the spacewalk >server from the client using yum, I don't 
> >know why it's giving a 500 error, and in reference to what.
>  
> To add a little more meat on the bones to this thanks to some help on irc.
>  
> if I tail the catalina.out log on the server and try to do an rhn_check on 
> the client, the log doesn't get updated, which I'd expect something as the 
> server is responding with a 500 error.
>  
> I can also communicate with the server from the client well, eg: I can do an 
> rhn-channels --list, I can install a package from the server on on the client 
> with yum, the spacewalk ui shows the client checking in, eg: registered at 
> 12:21, checked in at 12:51, so there is valid comms there, if I do an 
> rhn_register I'm told (rightly so) that the server is already registered, so 
> what could be causing the error 500 on the rhn_check ? I suspect this is the 
> same issue as the config files not being able to be deployed.
>  
> thanks,
>  
> Matt
>  
>  
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
> _______________________________________________
> Spacewalk-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/spacewalk-list


_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to