Mirror infrastructure problems?
Hi all, I seem to remember that there have recently been changes to the mirror infrastructure. I'm seeing problems with that, since maybe around one week. It manifests like that: Retrieving package btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64 (1/1192), 420,1 KiB ( 1,2 MiB unpacked) Retrieving: btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm ............................[not found] File './x86_64/btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/home:/seife:/testing/15.4' Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm ............................[not found] File './x86_64/btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/home:/seife:/testing/15.4' Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm ............................[not found] File './x86_64/btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/home:/seife:/testing/15.4' Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm ............................[done] Retrieving package fusefile-0.1~3_g1bfc0a7-lp154.1.1.x86_64 (2/1192), 11,9 KiB ( 11,4 KiB unpacked) Retrieving: fusefile-0.1~3_g1bfc0a7-lp154.1.1.x86_64.rpm ....................................[not found] File './x86_64/fusefile-0.1~3_g1bfc0a7-lp154.1.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/home:/seife:/testing/15.4' Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: fusefile-0.1~3_g1bfc0a7-lp154.1.1.x86_64.rpm ....................................[not found] File './x86_64/fusefile-0.1~3_g1bfc0a7-lp154.1.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/home:/seife:/testing/15.4' Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: fusefile-0.1~3_g1bfc0a7-lp154.1.1.x86_64.rpm .........................................[done] Retrieving package ipxe-bootimgs-1.21.1+git20210908.02ec659b-lp154.48.1.noarch (3/1192), 1,9 MiB ( 4,8 MiB unpacked) Retrieving: ipxe-bootimgs-1.21.1+git20210908.02ec659b-lp154.48.1.noarch.rpm .................[not found] File './noarch/ipxe-bootimgs-1.21.1+git20210908.02ec659b-lp154.48.1.noarch.rpm' not found on medium 'http://download.opensuse.org/repositories/home:/seife:/testing/15.4' Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: ipxe-bootimgs-1.21.1+git20210908.02ec659b-lp154.48.1.noarch.rpm ........[done (218,1 KiB/s)] So I'm getting a 404 for packages (or metadata also), and after retrying a few times (or just repeating the "zypper ref" a few times, it finally succeeds. This is mostly happening on "fringe" repos: my home project, CrossToolchain:avr, ..., only very seldom on the main opensuse repos. I'm guessing that I'm first redirected to a mirror which does not carry this repos (or is outdated) and after a few retries, I'm actually redirected to a "good" mirror. This can be up to 6 or 7 retries. Often, once a good mirror is found, more packages from the same repo can be downloaded without retry, but sometimes almost every single package needs retries (right now this is happening with http://download.opensuse.org/repositories/home:/seife:/vdrdevel/15.4) Is there a bugzilla category for such problems? Or should I just bounce this mail to admin@opensuse.org? Apparently I am not the only one seeing this as I have gotten reports that http://download.opensuse.org/repositories/vdr/15.4 would not carry binary packages only to get an update a few minutes later that retrying solved the issue. Best regards, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
Hi, Yes, there was an issue after an update; it is also reported e.g. in https://bugzilla.opensuse.org/show_bug.cgi?id=1200425 It should work properly now, please report infrastructure issues like this to heroes@ or mirror@ lists.
participants (2)
-
Andrii Nikitin
-
Stefan Seyfried