>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.
I've now got a pretty good grasp of what's going on, but I can't explain it.
When I'm kickstarting the client, it finish the build and registers with the
spacewalk server, however looking in the schedule tab, there are two actions
pending when the server is built.
1.) Activation key package auto install
2.) activation key config file deployment
now these two names seem pretty clear, 1.) installs the activation key, 2.)
deploys the config files (which is not happening)
a rhn_check at this time shows the error 500
[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]
however, if I delete these tasks and do an rhn_check, the error goes away and
the system checks in fine.
if I then do a config file deployment, it works fine.
So it's the initially running of those two jobs thats not happening, which if
you see the message I've put to the email list subject "Spacewalk 1.4 Oracle
SQL Error" may have an explaination for it, but I can't get my head around the
implications of that logs errors.
It does look like an SQL bug and advice/suggestions would be very much
appreicated
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
