Blacklist Zypper Mirror?

About 2 months ago I started having ridiculously low download speeds from the Argentina mirror (opensuse.unc.edu.ar). When manually downloading from any other latam server, the download speeds and response times are good.
Is there a way to blacklist the super slow mirror or to tell the cdn to test other servers from the pool if the speed is below a threshold?

It wasn’t like this at the beginning, I’m not sure if the server got slower or if a different mirror was used before

Post:
zypper lr -d

Not that I am aware of. You can tell MirrorCache to avoid specific country mirrors by appending ?AVOID_COUNTRY=xx parameter to the URL; but I am not sure how to setup repository so that zypper automatically does it.

Or you can prefer some country or region (?COUNTRY=xx or ?REGION=xx).

andrei@leap155:~/src/MirrorCache> grep url /etc/zypp/repos.d/repo-oss.repo
baseurl=http://download.opensuse.org/distribution/leap/$releasever/repo/oss/?AVOID_COUNTRY=jp
andrei@leap155:~/src/MirrorCache>

zypper will append the parameter(s) to each file request.

1 Like

I was almost faster when I had the 200 kbyte line than now that I have the 100 megabyte, and in the last year it has gotten worse. Everything comes in waves, I have been there for hours watching what was happening and every minute or so there is a peak that sometimes lasts a few seconds and then absolute zero not even a bit arrives. You can’t even say that it is slow, because it is not true, there are days that in a short time I download 2 Gigabytes, and days that to do an update you need the patience of the Eternal. I have made two posts about it without solving anything, whoever asks you for zypper lr -d and then starts saying this or that repo is not official, do this, do that they treat you like an idiot and in the end everything is as before

This is what happens to me, I launch zypper dup twice and the Packman repo times out twice, but that’s not all, everything takes a very long time, even the repo indexes don’t time out. The same thing happens during the update… because I’m in love with Opensuse, I used it for the first time 30 years ago, otherwise I would have already changed the distribution on the main computer too.

1 Like
> zypper lr -d
# | Alias                      | Name   | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                       | Service
--+----------------------------+--------+---------+-----------+---------+----------+--------+---------------------------------------------------------------------------+---------
1 | NVIDIA:repo-non-free       | repo-> | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://download.nvidia.com/opensuse/tumbleweed                           | NVIDIA
2 | X11_XOrg                   | X.Or-> | Yes     | (r ) Yes  | No      |   99     | rpm-md | https://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Tumbleweed/ | 
3 | openSUSE:repo-non-oss      | repo-> | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/non-oss                           | openSUSE
4 | openSUSE:repo-openh264     | repo-> | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed                   | openSUSE
5 | openSUSE:repo-oss          | repo-> | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/oss                               | openSUSE
6 | openSUSE:repo-oss-debug    | repo-> | No      | ----      | ----    |   99     | N/A    | http://cdn.opensuse.org/debug/tumbleweed/repo/oss                         | openSUSE
7 | openSUSE:repo-oss-source   | repo-> | No      | ----      | ----    |   99     | N/A    | http://cdn.opensuse.org/source/tumbleweed/repo/oss                        | openSUSE
8 | openSUSE:update-tumbleweed | upda-> | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://cdn.opensuse.org/update/tumbleweed                                 | openSUSE

I think this is it, I’ll try as soon as there’re new packages available for me. Regarding the repos themselves, while it can have something to do, I’ve not added new repositories since the problem started, and I’ve experienced the ridiculously low speeds through that specific mirror only, and its been months already

Using a VPN to make the system pick other mirrors seem to be enough to conclude that opensuse.unc.edu.ar is having throughput issues, and it’s been months like that already.
Is there a way I can report that mirror to be investigated? Tried on a different ISP and had the same experience.

One repo need not contain only one URL. You may replace the redirector URL with a group of URLs that you have observed are normally satisfactory. e.g.:

baseurl=http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/oss
	http://ftp.uni-erlangen.de/opensuse/tumbleweed/repo/oss
	http://www.gtlib.gatech.edu/pub/opensuse/tumbleweed/repo/oss
	http://provo-mirror.opensuse.org/tumbleweed/repo/oss

/etc/zypp/zypp.conf has this option available:

# grep min_ zypp.conf
 download.min_download_speed = 20000
#

By default it’s 0 and commented.

2 Likes

Thanks for the reply. adding the url param?AVOID_COUNTRY=arto the default url worked perfectly and seems like a simpler solution. It also works for manual downloads from downloads.opensuse.org.

But this is a workaround, it is certain that there’re problems with the only ar mirror and it should be removed, replaced or be left as a last resort regardless of distance and TTFB. It’s a bad experience for the low amount of users that are defaulted to it, and having to modify a system file doesn’t seem like the best option. There must be someone that could take a look at this specific mirror and escalate the issue, I’m not sure where to report it.

I’m not sure how Tumbleweed handles system overwrites but I’ve had my share of issues when modifying official repos on other distros when an update needed to change a modified file

1 Like

There are several ways to report infrastructure trouble. Specifically for mirrors there is a discussion mailing list. For general issues there is the heroes mailing list and also IRC - opensuse-admin. Issue reports can be made indirectly via the admin mailing list or directly.

1 Like

We are not responsible for mirror performance and issues. Anyone can become a mirror and send a request to become a registered mirror.

Ideally, the issue should be reported to UNC itself.

The only thing we can do on the openSUSE infra side is disable this mirror completely so users are never sent to it.

Zypper does not pick one single mirror for download during updates, it usually downloads from multiple sources. It could be that there are more mirrors in LATAM that don’t have a good performance. They can get slow if too many users are downloading at the same time.

On a side note, you can use mirrorsorcerer to control things on the system side.

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.