PDA

View Full Version : SLES 12 SP2 Server registation failed with yast2 and SUSEconnect



MaicT
31-May-2018, 11:42
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

malcolmlewis
31-May-2018, 13:42
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
Hi and welcome to the Forum :)
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

MaicT
31-May-2018, 13:55
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 `<main>'

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'?>
<stream>
<service-list>
<repo alias="SLES12-SP2-12.2-0" name="SLES12-SP2-12.2-0" type="yast2" priority="99" enabled="1" autorefresh="0" gpgcheck="1" repo_gpgcheck="1" pkg_gpgcheck="0">
<url>cd:///?devices=/dev/disk/by-id/ata-VMware_Virtual_IDE_CDROM_Drive_1000000000000000000 1</url>
</repo>
</service-list>
</stream>'

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

:(

Sincerly
Maic

thsundel
31-May-2018, 14:29
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 `<main>'

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'?>
<stream>
<service-list>
<repo alias="SLES12-SP2-12.2-0" name="SLES12-SP2-12.2-0" type="yast2" priority="99" enabled="1" autorefresh="0" gpgcheck="1" repo_gpgcheck="1" pkg_gpgcheck="0">
<url>cd:///?devices=/dev/disk/by-id/ata-VMware_Virtual_IDE_CDROM_Drive_1000000000000000000 1</url>
</repo>
</service-list>
</stream>'

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

:(

Sincerly
Maic

You are running the suseconnect command with root privileleges right?

Thomas

MaicT
04-Jun-2018, 09:02
You are running the suseconnect command with root privileleges right?

Thomas

Yes, I did it with root privileges.

Maic

MaicT
13-Jun-2018, 11:16
Nobody has a solution for me? :confused:
Is there another way to get the updates without registration?

Please help me :o
Maic

thsundel
13-Jun-2018, 11:33
Nobody has a solution for me? :confused:
Is there another way to get the updates without registration?

Please help me :o
Maic

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

Thomas

MaicT
13-Jun-2018, 12:35
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

HvdHeuvel
14-Jun-2018, 16:19
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

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

MaicT
15-Jun-2018, 07:32
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

Hi Hans,

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

uname –a

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

cat /etc/issue

Welcome to SUSE Linux Enterprise Server 12 SP2 (x86_64) - Kernel \r (\l).

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

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


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

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

Now I get a lot of data until the end with

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

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