Repository URLs are not accessible when using: zypper

Hello,

I have the following problem.

zypper ref and zypper in docker

do not work. Instead I get the following errormessages:

Dienst ‘Advanced_Systems_Management_Module_12_x86_64’ wird aktualisiert.
Problem beim Abrufen der Repository-Indexdatei für Dienst ‘Advanced_Systems_Management_Module_12_x86_64’:
Ungültiger Einhängepunkt des Mediums: https://scc.suse.com/access/services/

Bitte überprüfen Sie, ob der URI gültig und zugänglich ist.

In English that would mean sthg like:
Service ‘Advanced_Systems_Management_Module_12_x86_64’ will be updated.
Problem with the Repository-Index-file for service: ‘Advanced_Systems_Management_Module_12_x86_64’
Invalid Mount Point for the medium: https://scc.suse.com/access/services/

Please check if the URI is valid and accessible.

Do I need to add credentials somewhere on the server in order to submit the license to SUSE?

Any help appreciated since it is kind of a blocker
Thank you

On 19/04/16 17:14, MaxLuchs wrote:
[color=blue]

I have the following problem.

zypper ref and zypper in docker

do not work. Instead I get the following errormessages:

Dienst ‘Advanced_Systems_Management_Module_12_x86_64’ wird
aktualisiert.
Problem beim Abrufen der Repository-Indexdatei f�r Dienst
‘Advanced_Systems_Management_Module_12_x86_64’:
Ung�ltiger Einh�ngepunkt des Mediums:
https://scc.suse.com/access/services/

Bitte �berpr�fen Sie, ob der URI g�ltig und zug�nglich ist.

In English that would mean sthg like:
Service ‘Advanced_Systems_Management_Module_12_x86_64’ will be
updated.
Problem with the Repository-Index-file for service:
‘Advanced_Systems_Management_Module_12_x86_64’
Invalid Mount Point for the medium:
https://scc.suse.com/access/services/

Please check if the URI is valid and accessible.[/color]

Is the server registered with the SUSE Customer Center (SCC)? The URL
for the Advanced Systems Management Module seems suspect to me. What
does “zypper lr -u” report?

You should also note that Docker is provided from the Containers Module
so you’ll need to register with SCC to get access to that.

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

Hi, thanks for your answer.

The activation key has been added now.
But now only the SLES12-12-0 Repository is working.
All other repositories are not including the Container-Repository Containers_Module_12_x86_64

Any ideas how I get the other repositorys as well.

Normally they should be/are included in our license here.
Can I somehow fix the URLs of the other repository?

No actually the repository that worked was mounted. But not the online one.
How do I Register the Server @ Suse?

I have a SCCcredentials-file in /etc/zypp/credentials.d

But there is no SUSECOnnect-file in /etc

On 20/04/16 10:24, MaxLuchs wrote:
[color=blue]

No actually the repository that worked was mounted. But not the online
one.
How do I Register the Server @ Suse?

I have a SCCcredentials-file in /etc/zypp/credentials.d

But there is no SUSECOnnect-file in /etc[/color]

You need to either use the SUSEConnect command to register or do so via
YaST - please see
https://www.suse.com/documentation/sles-12/book_sle_deployment/data/sec_update_registersystem.html

The Containers module is free so registering SLES should give you access
to that though you’ll need to add it via SUSEConnect or YaST.

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.