SLES 11.3SP3 can't access repositories though its registered

SUSE Product Topics SLES Updates
1

Hi all,

Well, the title says it all. I installed SLES 11.3 SP3 and registered it. During registration through yast it shows the registration status as sucessfull. I can also see the machine being registered @ suse.com. During the registration it should download the repositories, which it doesn’t. The only repository I see is the DVD. Removing and re-registering either through yast or the command line doesn’t work either.
Also tried to add a repository using zypper (like: zypper ar https://updates.suse.com/repo/$RCE/SLES11-SP3-Updates/sle-11-i586 updates). This adds the repo but I still can’t access it, giving me an error: Permission to access ‘https://updates.suse.com/repo//SLES11-SP3-Updates/sle-11-i586/repodata/repomd.xml’ denied.
I went through the forums but wasn’t able to find a lot of usefull resolutions, the ones I found didn’t help.

So I’m kind of lost here about how to resolve it, anybody have any suggestions?

Thanks in advance.

2

Hi
De-register the system in SCC again and clean out the credentials
in /etc/zypp/credentials.d/ as in delete.

Then re-register and then run a zypper ref from the command line
and the repos should be added.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

3

[QUOTE=malcolmlewis;28092]Hi
De-register the system in SCC again and clean out the credentials
in /etc/zypp/credentials.d/ as in delete.

Then re-register and then run a zypper ref from the command line
and the repos should be added.
[/QUOTE]

What would the best way to re-register: yast or suse_register?

4

Hi tassitsupport,

What would the best way to re-register: yast or suse_register?

I’d say - whatever you are more comfortable with :wink: YaST2 gives you more suppport ui-wise, while suse_register gives you any and all CLI options you might want to employ. You decide.

Regards,
Jens

5

Ok guys, things I tried:

-de-registered the server in scc and removed the credential file locally

-Tried registering using suse_register that gave me an error and a success:

[CODE]Service ‘updates’
Execute command: /usr/bin/zypper --non-interactive ref --service
Execute command exit(4): Permission to access ‘https://updates.suse.com/repo//SLES11-SP3-Updates/sle-11-i586/repodata/repomd.xml’ denied.

Permission to access ‘https://updates.suse.com/repo//SLES11-SP3-Updates/sle-11-i586/content’ denied.

Repository ‘updates’ is invalid.
[|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository ‘updates’ because of the above error.
Some of the repositories have not been refreshed because of an error.
Execute command result: All services have been refreshed.
Retrieving repository ‘updates’ metadata [.
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
error]
Refresh failed(34): All services have been refreshed.
Retrieving repository ‘updates’ metadata [.
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
error]
Permission to access ‘https://updates.suse.com/repo//SLES11-SP3-Updates/sle-11-i586/repodata/repomd.xml’ denied.

Permission to access ‘https://updates.suse.com/repo//SLES11-SP3-Updates/sle-11-i586/content’ denied.

Repository ‘updates’ is invalid.
[|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository ‘updates’ because of the above error.
Some of the repositories have not been refreshed because of an error.
All services have been refreshed.
Retrieving repository ‘updates’ metadata [.
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
error]
Permission to access ‘https://updates.suse.com/repo//SLES11-SP3-Updates/sle-11-i586/repodata/repomd.xml’ denied.

Permission to access ‘https://updates.suse.com/repo//SLES11-SP3-Updates/sle-11-i586/content’ denied.

Repository ‘updates’ is invalid.
[|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository ‘updates’ because of the above error.
Some of the repositories have not been refreshed because of an error.
Ignored(34)
Registration finished successfully
[/CODE]

This was the repo I added manually. So I removed the repo and credentials again and tried it through yast.
I got forwarded to a webpage to enter my regcode and email address and after that the registration seemed successfull. The only thing is that there still was no repo added. In the details of the success message it stated something like ‘repositories do not need to be changed’

So I’m still facing the same challenge. Everything seems to go well but in the end I don’t get any repos added and can’t access updates.
bumps head against wall

6

Hi
I would use the command line suse_register and then run zypper ref.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

7

Hi Malcolm,

I posted some result, do they show? It seems they stick to the bottom of the page…

Anyway like said, both methods give a ‘success’ on registering but don’t add any repos. I’m still stuck with only my DVD repo.
Anything else I could try?

Thanks for your efforts so far.

8

Hi
Are the credentials present in /etc/zypp/credentials.d directory? NCC
and SCC?

If you force a refresh, do they get added;

zypper ref -f

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

9

[QUOTE=malcolmlewis;28111]Hi
Are the credentials present in /etc/zypp/credentials.d directory? NCC
and SCC?

If you force a refresh, do they get added;

zypper ref -f

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]

Hi Malcolm,

Yes, after deleting and re-registering a new NCCcredentials file is created and it contains a username and password.
When I issue the zypper ref -f I get the following:

Forcing raw metadata refresh Retrieving repository 'SUSE-Linux-Enterprise-Server-11-SP3 11.3.3-1.138' metadata [done] Forcing building of repository cache Building repository 'SUSE-Linux-Enterprise-Server-11-SP3 11.3.3-1.138' cache [done] All repositories have been refreshed.

The thing is that after that, I can still only see the DVD repository:

[CODE]zypper lr -d

| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service

–±-------------------------------------------------±-------------------------------------------------±--------±--------±---------±------±-------------------------------------------------------------------------------±-------
1 | SUSE-Linux-Enterprise-Server-11-SP3 11.3.3-1.138 | SUSE-Linux-Enterprise-Server-11-SP3 11.3.3-1.138 | Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/usb-PHILIPS_SPD3200L1_DEF10B6A832A-0:0,/dev/sr0 |
[/CODE]

I registered again with debugging turned on (suse_register -d 3 -a regcode-sles=xxxxxxxx -a email=myemail -a moniker=hostname -L suse_register-d3.log) but I can’t seem to find any errors in the logging.

10

Hi
Strange indeed, must be something with the interconnect between NCC and SCC…

If you try searching for something with zypper, eg;

zypper se libgpgme11

Does this start to add repositories? Else I think you may need to raise an SR.

11

Hi
Perhaps you want to try

suse_register --restor-repos

Running suse_register after having de-registered often does not enable repositories, that were there in the past.
//Andreas

12

On 02/06/2015 09:34, ataschner wrote:
[color=blue]

Perhaps you want to try

suse_register --restor-repos[/color]

Command is “suse_register --restore-repos” (restore with two "e"s) or
“suse_register -r”.

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.

13

Thanks Simon - obvious typo :slight_smile:
suse_register would error out with an “Unknown option : restor-repos” which hopefully could have lead the user to try “suse_register -h” and get the supported options listed…
//Andreas

14

[QUOTE=malcolmlewis;28120]Hi
Strange indeed, must be something with the interconnect between NCC and SCC…

If you try searching for something with zypper, eg;

zypper se libgpgme11

Does this start to add repositories? Else I think you may need to raise an SR.[/QUOTE]

Raising an SR could be somewhat difficult, I have a ‘download only’ subscription.

But…

I think I got it!

I already tried to add a repository manually (through Yast) using a URL like: https://updates.suse.com/repo/$RCE/SLES11-SP3_Pool/sle-11-x86_64 which kept giving me a 401.

After searching through the forums and google I came up with something worth a try. I tried adding a repo again but now I used the following URLs:
https://nu.novell.com/repo/$RCE/SLES11-SP3_Pool/sle-11-x86_64?credentials=NCCcredentials and https://nu.novell.com/repo/$RCE/SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials
Now the repos were added (yay!).

Through zypper I was now able to run an update, online update through Yast was still asking me to connect and get the repos. I’m not sure if running the updates or rebooting the server fixed that as well.
So indeed it look like there’s something quite wrong with the interconnection between ncc and scc.

But anyway, thanks for your support! :slight_smile:

15

Ok, this is getting weird.

The above solution worked on a virtual machine which I installed on the server that originally had the issues. Now I’m trying to do the same on that server but it is giving me errors.
In Yast it only says: ‘unable to create repository’, when I try to add the repo using zypper it seems to work until I want to use it:

[CODE]zypper ar -f https://nu.novell.com/repo/$RCE/SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials update
Adding repository ‘update’ [done]
Repository ‘update’ successfully added
Enabled: Yes
Autorefresh: Yes
GPG check: Yes
URI: https://nu.novell.com/repo//SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials

zypper lu
Retrieving repository ‘update’ metadata [error]
Repository ‘update’ is invalid.
[|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Disabling repository ‘update’ because of the above error.
Retrieving repository ‘updates’ metadata [error]
Repository ‘updates’ is invalid.
[|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Disabling repository ‘updates’ because of the above error.
Loading repository data…
Reading installed packages…
No updates found.[/CODE]

So there is some progress but we’re not quite there yet :stuck_out_tongue:

16

Hi tassitsupport,

[QUOTE=tassitsupport;28180]Ok, this is getting weird.

The above solution worked on a virtual machine which I installed on the server that originally had the issues. Now I’m trying to do the same on that server but it is giving me errors.
In Yast it only says: ‘unable to create repository’, when I try to add the repo using zypper it seems to work until I want to use it:

[CODE]zypper ar -f https://nu.novell.com/repo/$RCE/SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials update
Adding repository ‘update’ [done]
Repository ‘update’ successfully added
Enabled: Yes
Autorefresh: Yes
GPG check: Yes
URI: https://nu.novell.com/repo//SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials

zypper lu
Retrieving repository ‘update’ metadata [error]
Repository ‘update’ is invalid.
[|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Disabling repository ‘update’ because of the above error.
Retrieving repository ‘updates’ metadata [error]
Repository ‘updates’ is invalid.
[|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Disabling repository ‘updates’ because of the above error.
Loading repository data…
Reading installed packages…
No updates found.[/CODE]

So there is some progress but we’re not quite there yet :p[/QUOTE]

either quote the URL or escape the $ sign:

zypper ar -f https://nu.novell.com/repo/$RCE/SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials update
URI: https://nu.novell.com/repo//SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials

the shell replaced $RCE with the contents of the variable RCE :slight_smile:

Regards,
Jens

17

Yeah, I noticed that in the meantime (doh).

But even after correcting that, no luck:

[QUOTE]sx333:/storage/xenvm/windows7x64-1 # zypper ar -f https://nu.novell.com/repo/\$RCE/SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials update
Adding repository ‘update’ [done]
Repository ‘update’ successfully added
Enabled: Yes
Autorefresh: Yes
GPG check: Yes
URI: https://nu.novell.com/repo/$RCE/SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials

sx333:/storage/xenvm/windows7x64-1 # zypper lu
Retrieving repository ‘update’ metadata [error]
Repository ‘update’ is invalid.
[|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Disabling repository ‘update’ because of the above error.
Loading repository data…
Reading installed packages…
No updates found.
sx333:/storage/xenvm/windows7x64-1 # zypper lr -d

| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service

–±-------------------------------------------------±-------------------------------------------------±--------±--------±---------±------±--------------------------------------------------------------------------------------------±-------
1 | SUSE-Linux-Enterprise-Server-11-SP3 11.3.3-1.138 | SUSE-Linux-Enterprise-Server-11-SP3 11.3.3-1.138 | Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/usb-PHILIPS_SPD3200L1_DEF10B6A832A-0:0,/dev/sr0 |
2 | update | update | Yes | Yes | 99 | NONE | https://nu.novell.com/repo/$RCE/SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials |
[/QUOTE]

I noticed that the type for the repo was ‘NONE’, so I tried again adding the type to the command:

[QUOTE]sx333:/storage/xenvm/windows7x64-1 # zypper ar -t rpm-md -f https://nu.novell.com/repo/\$RCE/SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials update
Adding repository ‘update’ [done]
Repository ‘update’ successfully added
Enabled: Yes
Autorefresh: Yes
GPG check: Yes
URI: https://nu.novell.com/repo/$RCE/SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials

sx333:/storage/xenvm/windows7x64-1 # zypper lu
Retrieving repository ‘update’ metadata [\]
Timeout exceeded when accessing ‘https://nu.novell.com/repo/$RCE/SLES11-SP3_Updates/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials’.

Abort, retry, ignore? [a/r/i] (r):
Trying again…
Retrieving repository ‘update’ metadata [|]
Timeout exceeded when accessing ‘https://nu.novell.com/repo/$RCE/SLES11-SP3_Updates/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials’.

Abort, retry, ignore? [a/r/i] (r):
Autoselecting ‘r’ after 26 seconds.
Retrieving repository ‘update’ metadata [error]
Repository ‘update’ is invalid.
[|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Disabling repository ‘update’ because of the above error.
Loading repository data…
Reading installed packages…
No updates found.
sx333:/storage/xenvm/windows7x64-1 # zypper lr -d

| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service

–±-------------------------------------------------±-------------------------------------------------±--------±--------±---------±-------±--------------------------------------------------------------------------------------------±-------
1 | SUSE-Linux-Enterprise-Server-11-SP3 11.3.3-1.138 | SUSE-Linux-Enterprise-Server-11-SP3 11.3.3-1.138 | Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/usb-PHILIPS_SPD3200L1_DEF10B6A832A-0:0,/dev/sr0 |
2 | update | update | Yes | Yes | 99 | rpm-md | https://nu.novell.com/repo/$RCE/SLES11-SP3_Updates/sle-11-x86_64?credentials=NCCcredentials |
sx333:/storage/xenvm/windows7x64-1 #
[/QUOTE]

So now I get a timeout (?)

I checked on the VM that is working to see if the URL was still ok and yes, the /repodata/repomd.xml is there.

Strange that this is working on one machine and getting timeouts on the other :confused:

18

Hi tassitsupport,

I checked on the VM that is working to see if the URL was still ok and yes, the /repodata/repomd.xml is there.

have you tried to manually retrieve the file via wget or curl - maybe something is actually in the way, network-wise. Would you need to set a proxy that wasn’t configured on sx333 (but was set on the VM), or something similar?

Regards,
Jens

19

[QUOTE=jmozdzen;28183]Hi tassitsupport,

I checked on the VM that is working to see if the URL was still ok and yes, the /repodata/repomd.xml is there.

have you tried to manually retrieve the file via wget or curl - maybe something is actually in the way, network-wise. Would you need to set a proxy that wasn’t configured on sx333 (but was set on the VM), or something similar?

Regards,
Jens[/QUOTE]

We’re definitely thinking along the same lines here :slight_smile:
I checked the firewall and saw some packets being blocked when running zypper lu. But when I checked on the VM, the same messages appeared but the zypper command seemed to work without any errors.

So I have a host server that is installed using the virtualization host scenario that isn’t able to update. Then I got a guest VM on that server that is installed using the ‘physical server’ scenario that is working…
Could it have something to do with the fact that the host is booted with another kernel (xen)?
Or could it be that it has something to do with the fact that the host is using bridge interfaces and the guest isn’t (config directly in eth0)?

I’ll keep looking but would appreciate any additional insights.

20

Hi tassitsupport,

I’ll keep looking but would appreciate any additional insights

well, usually this boils down to either “the credentials are bogus” (which I for now will rule out, as the same work from within the VM) or “cannot access the URL”. To check the latter, I typically try to use some tool under my control (wget, curl) to access the URL in question manually, and evaluate its returns.

“zypper” doesn’t do any low-level magic - it just tries to fetch the files via the URL stem specified. OTOH, when there are proxies to be used, there are different ways to configure for the different tools and as I don’t do this every day, I need to look up which one needs which configure. IIRC, zypper uses libcurl, which in turn does check configuration files for proxy settings (see “man curl” for a list of config file locations checked) - so if that’s used inside the VM to set the proxy, that’d override any environment variable. OTOH, if no proxy is to be used, but set on sx333 somewhere, the request might fail as well.

Have you checked the zypper logs to see details of the HTML request, and tried manually (via wget, curl, browser - but making sure the request comes from the server in question, not ie browser on your PC :wink: )? If so, what were the results? Does the request need to go through a proxy and if so, does it log the request?

Regards,
Jens