Home_greyopenFATE - openSUSE feature tracking > #302923
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

handle redirection to mirrors robustly

Feature state

Rejected Information
Rejected Information


The proposal is to try other mirrors from a mirror list (from the redirector?) if an error occurs on some of the mirrors while providing a file from http/ftp repository. See the references for more details.









  • Paste "header=X-Broken-Mirrors" (without "") in ~/.aria2/aria2.conf. This should make the redirector to give you broken mirrors.
  • In zypp.conf : give download.max_silent_tries times a positive value, for example 5. This value tells how often zypp tries to connect to the mirror.
  • then try to install a package. You will never be able to download the file by testing this way, as the redirector will only give you broken mirrors.


icons/user_comment.png S. K. wrote: (10 years ago)

I would be strictly against having an own mirror list. The decision was to go with the redirector (or NCC for SLE) and be done with mirrors. If that does not work, then we have to do this whole thing again, not adding untested work arounds to the product.

icons/user_comment.png S. K. wrote: (10 years ago)

so I would reject this. But it's basically "Eval by Klaas" now

icons/user_comment.png K. F. wrote: (10 years ago)

I agree with Coolos and Peters statements, I would also reject.

icons/user_comment.png K. F. wrote: (9 years ago)

I have to revert my statement that I made before in comment #3, this problem is more serious than realised in the first look.

First, it should be noted that we do not control mirrors nor we do have the chance to really influence them. That means that if a mirrors decides to not longer mirror or to switch off or whatever, we have to live with it. However if a customer is sticky to a mirror that is not longer available he would not get any packages from it and thus installation or update fails. The worst thing about that is that this seems to happen regularly but we do not realise that because we're not involved.

A solution would be to have a list of possible mirrors that is used by the software installation stack to find a working mirror. Peter knows much more here.

But I am not sure at the moment if not Yast/zypper already has this functionality in 11.0?

icons/user_comment.png P. P. wrote: (9 years ago)

YaST/zypper in 11.1 will have preliminary support for this. The essential part
of http://en.opensuse.org/Libzypp/Failover has been implemented during a GSoC
project this year. See
http://lists.opensuse.org/zypp-devel/2008-09/msg00142.html for the status.

There is a number of things left to do, like

  • making it the default
  • better debuggability - show what it does
  • better progress report
  • testing
  • integration into the install system so it is available during installation

Further features from the proposal (mirror preference, simultaneous downloads)
are not tackled yet.

icons/user_comment.png F. L. wrote: (9 years ago)

I would like to see robust redirection, if possible. The details about a list, probably should not be in the feature description.

icons/user_comment.png T. R. wrote: (9 years ago)

Would this also be able to handle changes in the Buildservice, like renaming or moving of a certain Buildservice repository?

icons/user_comment.png P. P. wrote: (9 years ago)

No, that is outside the scope.
Changing repositories when the system is upgraded to a next major version is also outside the scope. Maybe that can be covered by http://en.opensuse.org/Standards/Repository_Index_Service , if I am not mistaking it.

icons/user_comment.png D. M. wrote: (9 years ago)

Today playing with aria (I am trying to switch the default in factory) I found out an interesting switch:


The first one ouputs the mirror statistics of the servers used, and the second one uses its as input:

cat stats
host=download.opensuse.org, protocol=http, dl_speed=0, last_updated=1233674714, status=OK
host=widehat.opensuse.org, protocol=http, dl_speed=8525008, last_updated=1233674714, status=OK

It may make sense to make the MediaAria backend to store this in var/cache/zypp and use it as input for next time too.

icons/user_comment.png D. M. wrote: (8 years ago)

This feature is done, see the blog posts in the references.

everything else, bugzilla.

icons/user_comment.png J. K. wrote: (8 years ago)

People, you keep writing zypper.conf to the test case. There's NO SUCH OPTION in zypper.conf as download.max_silent_retries; this is in zypp.conf!

Last change: 8 years ago
Loading tags...
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint