Server registation failed with yast2 and SUSEconnect

SUSE Product Topics SLES Updates
1

Hello,

please help me fixing a problem with the registration of a new installed server.
With yast2 it didn´t work.
We found out, that our proxy let the connection through.
I found the command SUSEConnect and tried this way for the registration.
I tried

“SUSEConnect -r 12345678901234 -e maic@example.de -u https://scc.suse.com -debug”

and got the following error.

“SUSEConnect error: SUSE::Connect::CannotBuildBasicAuth: Cannot read username and password from /etc/zypp/credentials.d/SCCcredentials”

I don´t understand why.
The missed data would be saved after the registration, I think.
The server was de-registered and not seen in our profile.
What ist wrong with this command?

Thank you in advance.

Maic

1 Like
2

[QUOTE=MaicT;52810]Hello,

please help me fixing a problem with the registration of a new installed server.
With yast2 it didn´t work.
We found out, that our proxy let the connection through.
I found the command SUSEConnect and tried this way for the registration.
I tried

“SUSEConnect -r 12345678901234 -e maic@example.de -u https://scc.suse.com -debug”

and got the following error.

“SUSEConnect error: SUSE::Connect::CannotBuildBasicAuth: Cannot read username and password from /etc/zypp/credentials.d/SCCcredentials”

I don´t understand why.
The missed data would be saved after the registration, I think.
The server was de-registered and not seen in our profile.
What ist wrong with this command?

Thank you in advance.

Maic[/QUOTE]
Hi and welcome to the Forum :slight_smile:
Did you try deregistering again and also clean up via SUSEConnect?

SUSEConnect --de-register --debug
SUSEConnect --cleanup --debug
SUSEConnect -r 12345678901234 -e maic@example.de -u https://scc.suse.com --debug
3

Hello

and thank you for your reply. :o

Yes and now again with These answers.

SUSEConnect --de-register --debug
cmd options: ‘{:deregister=>true, :debug=>true, :language=>“POSIX”}’
Merged options: #<SUSE::Connect::Config insecure=false, url=“https://scc.suse.com”, deregister=true, debug=true, language=“POSIX”>
SUSEConnect error: SUSE::Connect::CannotBuildBasicAuth: Cannot read username and password from /etc/zypp/credentials.d/SCCcredentials
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/toolkit/utilities.rb:23:in rescue in system_auth' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/toolkit/utilities.rb:12:in system_auth’
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/client.rb:36:in deregister!' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/cli.rb:26:in execute!’
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/bin/SUSEConnect:11:in <top (required)>' /usr/sbin/SUSEConnect:23:in load’
/usr/sbin/SUSEConnect:23:in `’

SUSEConnect --cleanup --debug
cmd options: ‘{:cleanup=>true, :debug=>true, :language=>“POSIX”}’
Executing: ‘zypper --xmlout --non-interactive services -d’ Quiet: false
Output: ’<?xml version='1.0'?>



cd:///?devices=/dev/disk/by-id/ata-VMware_Virtual_IDE_CDROM_Drive_10000000000000000001


’

SUSEConnect -r 12345678901234 -e maic@example.de -u https://scc.suse.com -debug
SUSEConnect error: SUSE::Connect::CannotBuildBasicAuth: Cannot read username and password from /etc/zypp/credentials.d/SCCcredentials

:frowning:

Sincerly
Maic

4

[QUOTE=MaicT;52813]Hello

and thank you for your reply. :o

Yes and now again with These answers.

SUSEConnect --de-register --debug
cmd options: ‘{:deregister=>true, :debug=>true, :language=>“POSIX”}’
Merged options: #<SUSE::Connect::Config insecure=false, url=“https://scc.suse.com”, deregister=true, debug=true, language=“POSIX”>
SUSEConnect error: SUSE::Connect::CannotBuildBasicAuth: Cannot read username and password from /etc/zypp/credentials.d/SCCcredentials
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/toolkit/utilities.rb:23:in rescue in system_auth' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/toolkit/utilities.rb:12:in system_auth’
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/client.rb:36:in deregister!' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/cli.rb:26:in execute!’
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/bin/SUSEConnect:11:in <top (required)>' /usr/sbin/SUSEConnect:23:in load’
/usr/sbin/SUSEConnect:23:in `’

SUSEConnect --cleanup --debug
cmd options: ‘{:cleanup=>true, :debug=>true, :language=>“POSIX”}’
Executing: ‘zypper --xmlout --non-interactive services -d’ Quiet: false
Output: ’<?xml version='1.0'?>



cd:///?devices=/dev/disk/by-id/ata-VMware_Virtual_IDE_CDROM_Drive_10000000000000000001


’

SUSEConnect -r 12345678901234 -e maic@example.de -u https://scc.suse.com -debug
SUSEConnect error: SUSE::Connect::CannotBuildBasicAuth: Cannot read username and password from /etc/zypp/credentials.d/SCCcredentials

:frowning:

Sincerly
Maic[/QUOTE]

You are running the suseconnect command with root privileleges right?

Thomas

5

[QUOTE=thsundel;52815]You are running the suseconnect command with root privileleges right?

Thomas[/QUOTE]

Yes, I did it with root privileges.

Maic

6

Nobody has a solution for me? :confused:
Is there another way to get the updates without registration?

Please help me :o
Maic

7

[QUOTE=MaicT;53018]Nobody has a solution for me? :confused:
Is there another way to get the updates without registration?

Please help me :o
Maic[/QUOTE]

Maybe this, looks similar: https://www.novell.com/support/kb/doc.php?id=7022424 ?
Or maybe open a Service Request.

Thomas

8

Thx Thomas.

That is a problem.
We bought SLES only with updates ans no support (Basic subscription).
Now we aren´t able to get the updates.
Someone from SUSE wrote me, to use this forum.
It sounds “(Get your questions answered by professionals)”.
What can a customer do, if nobody knows a way to fix this issue?
It is nice, that malcolmlewis and thsundel try to help me.
But unfortunately no one from Suse.
I´m running in a circle.

Maic

9

[QUOTE=MaicT;53021]Thx Thomas.

That is a problem.
We bought SLES only with updates ans no support (Basic subscription).
Now we aren´t able to get the updates.
Someone from SUSE wrote me, to use this forum.
It sounds “(Get your questions answered by professionals)”.
What can a customer do, if nobody knows a way to fix this issue?
It is nice, that malcolmlewis and thsundel try to help me.
But unfortunately no one from Suse.
I´m running in a circle.

Maic[/QUOTE]

Hi Maic,

The machine was registered before, but fails to register on another attempt now you try to re-register ?
Is that correct ?

What (exact) SLE version is this ?

Can you allow this server to register directly to SCC w/o your proxy interfering ?
Can you sent me a direct email to “hvdheuvel [at] suse [dot] com” and provide me with your SLE registration code and the email address used for registration ?

I can try and check the SCC back-end for you, but fear this is an issue with your proxy

Best regards
Hans

10

[QUOTE=HvdHeuvel;53052]Hi Maic,

The machine was registered before, but fails to register on another attempt now you try to re-register ?
Is that correct ?

What (exact) SLE version is this ?

Can you allow this server to register directly to SCC w/o your proxy interfering ?
Can you sent me a direct email to “hvdheuvel [at] suse [dot] com” and provide me with your SLE registration code and the email address used for registration ?

I can try and check the SCC back-end for you, but fear this is an issue with your proxy

Best regards
Hans[/QUOTE]

Hi Hans,

I am glad to hear from you, as an employee from SUSE. :slight_smile:
You are right, this server was registered sometimes before.
It is fresh installed with SLES 12.

[COLOR=#ff0000]uname –a[/COLOR]

[COLOR=#0000ff]Linux test 4.4.21-69-default #1 SMP Tue Oct 25 10:58:20 UTC 2016 (9464f67) x86_64 x86_64 x86_64 GNU/Linux
[/COLOR]
[COLOR=#ff0000]cat /etc/issue[/COLOR]

[COLOR=#0000ff]Welcome to SUSE Linux Enterprise Server 12 SP2 (x86_64) - Kernel \r (\l).
[/COLOR]
Because you think about a problem with our proxy, I tried to get the error messages again.
In the past we saw, that the command was going through the proxy.
I tried

[COLOR=#ff0000]SUSEConnect -r 12345678901234 -e maic@example.de -u https://scc.suse.com -debug[/COLOR]

and got the following error.
[COLOR=#0000ff]
SUSEConnect error: SUSE::Connect::CannotBuildBasicAuth: Cannot read username and password from /etc/zypp/credentials.d/SCCcredentials[/COLOR]

It´s the same like the one in my first post!

After that I looked again to the explanation oft he SUSEConnect command and tried

[COLOR=#ff0000]SUSEConnect -r 12345678901234 -e maic@example.de -u https://scc.suse.com –debug[/COLOR]

Now I get a lot of data until the end with

[COLOR=#0000ff]Output: ‘Refreshing service ‘SUSE_Linux_Enterprise_Server_12_SP2_x86_64’.
Adding repository ‘SLES12-SP2-Source-Pool’ […done]
Adding repository ‘SLES12-SP2-Debuginfo-Pool’ […done]
Adding repository ‘SLES12-SP2-Pool’ […done]
Adding repository ‘SLES12-SP2-Debuginfo-Updates’ […done]
Adding repository ‘SLES12-SP2-Updates’ […done]
Specified services have been refreshed.’
Registered SLES 12.2 x86_64
To server: https://scc.suse.com
Using E-Mail: maic@example.de[/COLOR]

So I got the registration finished.

I don´t understand, why the wrong option gives a misleading error message.
It does´t matter at all, because I got updates now. :cool:

Thanks a lot to all of you, who tried to help me.
Have a great time.

Cu
Maic

11

I have the same problem. I tried what you have wrote but How did you manage the proxy problem?