What do you see if you run rhn-profile-sync manually on the client? Might be interesting to run that with "strace -f" to see exactly what it's attempting to gather and send to Spacewalk.
On Thu, Mar 31, 2016 at 8:59 PM Eric B <[email protected]> wrote: > All, hope somebody may have some insight on this issue. > > New Spacewalk Build, all current pkgs. I cofigured a channel for RHEL 6, > synced it against a repo, and registered RHEL 6 client systems to it with > no issues. I used only Redhat client side tools as provided in the > rhn_tools channel. No issues, everything works as expected. > > I used the same process for RHEL 5. Created a RHEL 5 channel, IA32 > architecture (clients are x86). However, when I attempt to register a > client, on the client side, khn_register returns "internal server error". > The up2date log on the clients logs communication errors. When I tail the > Spacewalk logs on the server, I can watch it connect, pass the token, but > it the following error appears in the log: > > > xmlrpc/registration.__add_hw_profile_no_auth > > Also, if I look in the spacewalk systems list, I see the new system, but I > cannot manage it at all, and the client does not show as registered. > > I am not kickstarting, or using profiles, simply registering using a > activation key. > > Thanks for any help, been pounding my head on this all day. > > Eric > > Happy Connecting. Sent from my Sprint Samsung Galaxy S® 5 Sport > _______________________________________________ > 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
