PDA

View Full Version : Client errors when registrering with SUSEManager server



plaubscher
06-May-2016, 14:22
To whom it may concern

1. I am trying to register two clients.From the SUSEManager server the register process, takes place without any problem.

cd /srv/www/htdocs/pub/bootstrap/ cat bootstrap-edited.sh | ssh root@client_server_name /bin/bash

1.1 But on the one Client server, I am getting the following error.No firewall are enabled on both servers.

CHECKING THE REGISTRATION STACK
-------------------------------------------------
* check for necessary packages being installed...
* client codebase is sle-11-sp2
spacewalk-check-1.7.14.19-0.5.3
spacewalk-client-setup-1.7.14.19-0.5.3
spacewalk-client-tools-1.7.14.19-0.5.3
zypp-plugin-spacewalk-0.9.8-0.6.2.3
no packages missing.
* running the update scripts
. up2date config file

REGISTRATION
------------
* registering
Error communicating with server. The message was:
Internal Server Error

*** Error: Registering the system failed.

1.3 The Second client error :

CHECKING THE REGISTRATION STACK
-------------------------------------------------
* check for necessary packages being installed...
* client codebase is sle-11-sp3
spacewalk-check-2.1.16.10-15.2
spacewalk-client-setup-2.1.16.10-15.2
spacewalk-client-tools-2.1.16.10-15.2
zypp-plugin-spacewalk-0.9.12-18.3
no packages missing.
* running the update scripts
. up2date config file

REGISTRATION
------------
* registering
Traceback (most recent call last):
File "/usr/sbin/rhnreg_ks", line 25, in <module>
from rhn.connections import idn_pune_to_unicode
ImportError: No module named rhn.connections

*** Error: Registering the system failed.

Can somebody help with these errors ?

malcolmlewis
06-May-2016, 14:57
Hi
Make sure your SuMA instance is up to date, then ensure the client that registered is also up to date vai SuMA. Then try re-registering the failing system.

plaubscher
09-May-2016, 14:49
Yes SuMA is up to date.I managed to registered 6 Clients.I recreated my activation keys for all my channels and used only the defaults when creating the activation keys.

kwk
10-May-2016, 09:00
"ImportError: No module named rhn.connections" looks like you mixed up package versions for the client stack. Without further information it's next to impossible to find out why.
I'd suggest to open a service request and add supportconfig data for server (for the log files) and client (for the package versions).

jan_foerster
06-Jul-2016, 07:13
Same problem here while registering SLES12SP1 client on a proxy site. Was there a SR and/or solution to this issue?
SuMA and Proxy are up to date.

ScorpionSting
11-Jul-2016, 03:15
Had the same issue...the bootstrap script doesn't actually install all the needed RPMs....there were 2 rpm's I had to copy over and install, then re-ran the bootstrap script and all was well in the world...

Off the top of my head, I think it was these two:

suseRegisterInfo-3.0.2-18.1.x86_64
rhnlib-2.5.84.2-11.1.noarch

jan_foerster
13-Jul-2016, 11:52
Had the same issue...the bootstrap script doesn't actually install all the needed RPMs....there were 2 rpm's I had to copy over and install, then re-ran the bootstrap script and all was well in the world...

Off the top of my head, I think it was these two:

suseRegisterInfo-3.0.2-18.1.x86_64
rhnlib-2.5.84.2-11.1.noarch

Hi ScorpionSting,

this worked for us! Thank you for helping us!