Hopefully this will assist, a shot in the dark... Most of the following is from a kickstart. The !! comments and actions are additional steps that may or may not be needed. Try reinstalling the following on the client side. <tt># below pkgs needed for rhn registration and configuration management rhn-check rhnsd rhn-setup rhn-client-tools yum-rhn-plugin libidn rhncfg rhncfg-client rhncfg-actions libxml2 pyOpenSSL libxml2-python rhnlib perl</tt>When using a kickstart, there are some additional items that are completed besides installing the RPMs. <tt>mkdir -p /etc/sysconfig/rhn/allowed-actions/script touch /etc/sysconfig/rhn/allowed-actions/script/run mkdir -p /etc/sysconfig/rhn/allowed-actions/configfiles touch /etc/sysconfig/rhn/allowed-actions/configfiles/all</tt> <tt>/etc/init.d/messagebus restart /etc/init.d/haldaemon restart</tt> <tt># begin Red Hat management server registration</tt> <tt>mkdir -p /usr/share/rhn/ wget </tt><a href="http://dev-uprrsat.sos.tla.uprr.com/pub/RHN-ORG-TRUSTED-SSL-CERT"><a href=http://myspacewalk/><tt>http://MySpacewalk</tt></a><tt>.com/pub/RHN-ORG-TRUSTED-SSL-CERT</tt></a><tt>-O /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT perl -Xnpe 's/RHNS-CA-CERT/RHN-ORG-TRUSTED-SSL-CERT/g' -i /etc/sysconfig/rhn/* </tt> <tt>!! This may not be needed in your case if [ -f /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release ]; then rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release fi</tt> <tt> key=kickstart-key,my-custom_key if [ -f /tmp/key ]; then key=`cat /tmp/key`,$key fi </tt> <tt>!! Not from a kickstart..</tt> <tt>!! Before registering... Validate the date/time on the server. It can cause failures as well. !! date !! service ntpd stop !! ntpdate -s Myntpservers !! service ntpd start</tt> <tt>rhnreg_ks --serverUrl=https://MySpacewalk.com/XMLRPC --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=$key</tt> <tt># end Red Hat management server registration # end cobbler snippet rhn_check</tt> - Thanks and good luck From: Avi Miller <avi.miller@oracle.com> To: spacewalk-list@redhat.com Date: 02/27/2017 10:55 PM Subject: Re: [Spacewalk-list] Adding system to Spacewalk Sent by: spacewalk-list-bounces@redhat.com <hr noshade> <tt>This email originated from outside of the company. Please use discretion if opening attachments or clicking on links. Hi, > On 28 Feb 2017, at 3:30 pm, InvalidPath <invalid.path@gmail.com> wrote: > >> self._connection.connect() >> File "/usr/lib/python2.4/site-packages/rhn/connections.py", line 185, in >> connect >> if e.errno != errno.EINTR: I’ve never seen this error before, to be honest. >> Let me ask a stupid question, does the fact that I do not have a RH >> subscriptions for up2date, nor the red Hat Network matter in the use of >> Spacewalk? No it doesn’t. > Well after some time Googling I discovered that I might need osad > installed and running, so I did. Re-ran the rhnreg_ks command with > the same cryptic returns. Osad only works once you’ve successfully registered with Spacewalk. Are there any errors in /var/log/rhn/* or /var/log/httpd/* or /var/log/tomcat/* on your Spacewalk box that might shed some light on this? Cheers, Avi -- Oracle <</tt><a href=http://www.oracle.com/><tt>http://www.oracle.com</tt></a><tt>> Avi Miller | Product Management Director | +61 (3) 8616 3496 Oracle Linux and Virtualization 417 St Kilda Road, Melbourne, Victoria 3004 Australia _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com </tt><a href="https://www.redhat.com/mailman/listinfo/spacewalk-list"><tt>https://www.redhat.com/mailman/listinfo/spacewalk-list</tt></a> ** This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient. Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law. If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies. **