One client unable to register

SUSE Manager
1

Hi all,

I’m trying Suse Manager out and think it’s working fairly ok.
My Suse manager server is sitting on a public ip in a datacenter behind a firewall. My test clients are sitting on a other location behind a firewall that only has one ip and is doing ip masqurading for all traffic going out from that network.
Of my 3 test server two connects allright when I register them but one gives a error when register. The server that fails throws this error
"REGISTRATION

  • registering
    An error has occurred:
    Error communicating with server. The message was:
    Connection timed out on readline
    See /var/log/up2date for more information "
    The server ends up in the Suse Manager interface as a registered but never check in again.
    I have manually updated server with latest patches, the server can connect over http and https.
    It sles11sp3/oes11sp2 (fully patched), when I capture some traffic with wireshark I see multiple TLSv1 encryption alert from server and right after that a tcp rst from client. Don’t know if that causing the timeout, since other clients works fine with the certificate and bootstrap comman I think it shoul be allright.
    Any suggestions?

/Lennart

2

Hi,

did you have a look at /var/log/up2date ?
if this error appears only on one of three machines, this looks like a network/firewall issue.

Full documentation is available at https://www.suse.com/documentation/suse_manager/

3

Hi, yes I looked in up2date log file. It dosn’t say me much, it referencing a lot of phyton scripts and ends with
“<class ‘up2date_client.up2dateErrors.CommunicationError’>: Error communicating with server. The message was:
Internal Server Error”
Client setup is as follows.
Xen dom0 server with Sles11sp2, registing fine reciving patches
Xen domU sles 11sp3/oes11sp2, registering fine reciving patches.
Xen domU sles 11sp3/oes11sp2, Suse Manager thinks its registred, client say register failed. not receiving updates.
No problem initiating registration, can do http/https to suse manager.
No firewall in any instance.

4

Uhm, that’s confusing. Are you saying that one 11sp3 client is working fine, while the other is not ?
What is the difference between both clients ?
And how many clients are connected to the SUSE Manager server ?

5

Hi,

yes thats right, the only real difference is that the server failing to register is running Novell DSFWQ and the one working is not.
This is the first clients thats is connected.
Thanks for your help

/Lennart

6

[QUOTE=lelle;25062]the only real difference is that the server failing to register is running Novell DSFWQ and the one working is not.
[/QUOTE]

Hmm, Novell DSFWQ shouldn’t have any influence ?

Is the SUSE Manager running with an evaluation subscription ? Then you might have run into the max. number of clients.

If you have a full subscription, please open a support request and attach the /var/log/up2date log file.

7

Hi,

Stuck with my fingers in the keyboard, meant DSFW.
Yes I have opened a SR, no solution yet.

/Lennart

[QUOTE=kwk;25078]Hmm, Novell DSFWQ shouldn’t have any influence ?

Is the SUSE Manager running with an evaluation subscription ? Then you might have run into the max. number of clients.

If you have a full subscription, please open a support request and attach the /var/log/up2date log file.[/QUOTE]

8

[QUOTE=lelle;25062]yes thats right, the only real difference is that the server failing to register is running Novell DSFWQ and the one working is not.
This is the first clients thats is connected.[/QUOTE]

Hi Lennart,

I’m curious what this turns out to be. As a basic first, DNS resolving (manager to client and client to manager) is always one to watch for (and possible if the DSfW server might be somewhat more isolated in it’s own DNS).

These slides might prove useful (from a session given at SUSECon full with good info and troubleshooting steps) : https://susecon2014.smarteventscloud.com/connect/fileDownload/session/41A9AD7133F2979D5C00DF9A839209BF/TUT8120__-TUT8120.pdf

Cheers,
Willem

9

On the client
does this work
#zypper lr

try
rm /etc/zypp/credentials.d/NCCcredentials
suse_register -i -r

then rerun your bootstrap