Project

General

Profile

Actions

tickets #112985

closed

Fwd: opensuse server issues going on now ?

Added by bittin almost 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Mirrors
Target version:
-
Start date:
2022-06-24
Due date:
% Done:

100%

Estimated time:

Description

---------- Forwarded message ----------
From: Joe Salmeri jmscdba@gmail.com
Date: Thu, 23 Jun 2022 18:23:02 -0000
Subject: opensuse server issues going on now ?
To: factory@lists.opensuse.org

I was attempting to update to the new 20220622 build that was just published.

I use tumbleweed-cli to control which build I switch to.

In does not show a new build as available until after the build has
been copied to a build folder ( example:
https://download/opensuse.org/history20220622 )

I switched tumbleweed-cli to build 20220622, here are my repoositories:

Repository priorities in effect:
(See
'zypper lr -P' for details)
90 (raised priority) : 1 repository
99 (default priority) : 7 repositories

| Alias | Name

Enabled GPG Check Refresh URI
1 download.opensuse.org-non-oss Main Repository (NON-OSS)
(20220622) Yes (r ) Yes Yes

http://download.opensuse.org/history/20220622/tumbleweed/repo/non-oss/
2 | download.opensuse.org-oss | Main Repository (DEBUG)
| Yes | (r ) Yes | Yes |
http://download.opensuse.org/debug/tumbleweed/repo/oss/
3 | download.opensuse.org-oss_1 | Main Repository (Sources)
| Yes | (r ) Yes | Yes |
http://download.opensuse.org/source/tumbleweed/repo/oss/
4 | download.opensuse.org-oss_2 | Main Repository (OSS)
(20220622) | Yes | (r ) Yes | Yes |
http://download.opensuse.org/history/20220622/tumbleweed/repo/oss/
5 | download.opensuse.org-tumbleweed | Main Update Repository
| Yes | (r ) Yes | Yes |
http://download.opensuse.org/update/tumbleweed/
6 | google-chrome | google-chrome
| Yes | (r ) Yes | Yes |
https://dl.google.com/linux/chrome/rpm/stable/x86_64
7 | openSUSE-20210215-0 | openSUSE-20210215-0
| No | ---- | ---- |
cd:/?devices=/dev/disk/by-id/ata-VMware_Virtual_IDE_CDROM_Drive_10000000000000000001
8 | skype-stable | skype (stable)
| Yes | (r ) Yes | Yes |
https://repo.skype.com/rpm/stable/
9 | vlc | VLC
| Yes | (r ) Yes | Yes |
http://download.videolan.org/pub/vlc/SuSE/Tumbleweed/

zypper dup or zypper refresh fails with:

Retrieving repository 'Main Repository (NON-OSS) (20220622)' metadata
...........................................................................................[error]
Repository 'Main Repository (NON-OSS) (20220622)' is invalid.
[download.opensuse.org-non-oss|http://download.opensuse.org/history/20220622/tumbleweed/repo/non-oss/]
Valid metadata not found at specified URL
History:

Please check if the URIs defined for this repository are pointing to a
valid repository.
Skipping repository 'Main Repository (NON-OSS) (20220622)' because of
the above error.
Retrieving repository 'Main Repository (DEBUG)' metadata
........................................................................................................[error]
Repository 'Main Repository (DEBUG)' is invalid.
[download.opensuse.org-oss|http://download.opensuse.org/debug/tumbleweed/repo/oss/]
Valid metadata not found at specified URL
History:

Please check if the URIs defined for this repository are pointing to a
valid repository.
Skipping repository 'Main Repository (DEBUG)' because of the above error.
Retrieving repository 'Main Repository (Sources)' metadata
......................................................................................................[error]
Repository 'Main Repository (Sources)' is invalid.
[download.opensuse.org-oss_1|http://download.opensuse.org/source/tumbleweed/repo/oss/]
Valid metadata not found at specified URL
History:

Please check if the URIs defined for this repository are pointing to a
valid repository.
Skipping repository 'Main Repository (Sources)' because of the above error.
Retrieving repository 'Main Repository (OSS) (20220622)' metadata
...............................................................................................[error]
Repository 'Main Repository (OSS) (20220622)' is invalid.
[download.opensuse.org-oss_2|http://download.opensuse.org/history/20220622/tumbleweed/repo/oss/]
Valid metadata not found at specified URL
History:

Please check if the URIs defined for this repository are pointing to a
valid repository.
Skipping repository 'Main Repository (OSS) (20220622)' because of the
above error.
Repository 'Main Update Repository' is up to date.
Repository 'google-chrome' is up to date.
Repository 'skype (stable)' is up to date.
Repository 'VLC' is up to date.
Some of the repositories have not been refreshed because of an error.

If I go to the one of the 20220622 download locations in Chrome

https://download.opensuse.org/history/20220622/tumbleweed/repo/oss/x86_64/

And then try to manually download a single item like:

konsole-22.04.2-1.1.x86_64.rpm

It returns:

This site can’t be reached

mirrorcache-us.opensuse.org refused to connect.

I have a direct internet connection ( No proxy ) so it appears that
there is a problem with the cache servers.

Going to an older build like 20220606 which is what I am currently
running has the same issues so that eliminates that 20220622 had not
finished copying yet.

Anybody else seeing this?


Related issues 1 (0 open1 closed)

Related to openSUSE admin - tickets #112967: mirrorcache-us.opensuse.org is downResolved2022-06-23

Actions
Actions #1

Updated by pjessen almost 2 years ago

Actions #2

Updated by pjessen almost 2 years ago

  • Assignee set to andriinikitin
  • Private changed from Yes to No

Apart from :

mirrorcache-us.opensuse.org refused to connect.

I think this is a question for a support forum, not really about our infrastructure. In the meantime "mirrorcache-us.opensuse.org" appears to be up and running again, regrettably I have no further details. Andrii, do you have any additional information ?

Actions #3

Updated by lrupp almost 2 years ago

  • Category set to Mirrors
Actions #4

Updated by andriinikitin almost 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

There was ~30 min downtime back then caused by failed update of US proxy server. It should work properly now so I am closing the call as resolved.

Actions

Also available in: Atom PDF