mirror system broken.
problem in kernel mirrors (et al) Asked for: 389-ds-2.0.10~git0.21dd2802c-1.1.x86_64.rpm from: http:download.opensuse.org Got Miss/302 (redirect) +0.17 164㎳; 2002 (12K/12K) MISS/302 <Ishtar [GET http://download.opensuse.org/tumbleweed/repo/oss/x86_64/389-ds-2.0.10~git0.2... - 195.135.221.134 text/html] to sfo-korg-mirror gave "moved permanently"(301) +0.03 19㎳; 295 (13K/15K) MISS/301 <Ishtar [GET http://sfo-korg-mirror.kernel.org/opensuse/tumbleweed/repo/oss/x86_64/389-ds... - 149.20.37.36 -] and tried https on mirrors.edge.k.o: https://mirrors.edge.kernel.org/opensuse/tumbleweed/repo/oss/x86_64/389-ds-2... THAT HAD NO COPY and returned 404 (instead of forwarding) The 404 in my squidlog, BTW, was hidden in the https/tunnel which is why this is a pain to track down. I caught it in my browser which ended up on their 404 page: (Sorry, we cannot find your kernels) the 301 (permanently moving) kills forwarding to the next mirror if it isn't present (another variable, if it is present, will work, if not, won't).
On Sat, 2021-09-25 at 01:46 -0700, L A Walsh wrote:
problem in kernel mirrors (et al)
Asked for: 389-ds-2.0.10~git0.21dd2802c-1.1.x86_64.rpm from: http:download.opensuse.org
Got Miss/302 (redirect) +0.17 164㎳; 2002 (12K/12K) MISS/302 <Ishtar [GET http://download.opensuse.org/tumbleweed/repo/oss/x86_64/389-ds-2.0.10~git0.2... - 195.135.221.134 text/html]
to sfo-korg-mirror gave "moved permanently"(301)
+0.03 19㎳; 295 (13K/15K) MISS/301 <Ishtar [GET http://sfo-korg-mirror.kernel.org/opensuse/tumbleweed/repo/oss/x86_64/389-ds... - 149.20.37.36 -]
and tried https on mirrors.edge.k.o:
https://mirrors.edge.kernel.org/opensuse/tumbleweed/repo/oss/x86_64/389-ds-2...
THAT HAD NO COPY and returned 404 (instead of forwarding)
The 404 in my squidlog, BTW, was hidden in the https/tunnel which is why this is a pain to track down.
I caught it in my browser which ended up on their 404 page: (Sorry, we cannot find your kernels)
the 301 (permanently moving) kills forwarding to the next mirror if it isn't present (another variable, if it is present, will work, if not, won't).
Linda, this mailinglist is not the appropriate place to report issues with mirrors The correct mailinglist would be mirror@lists.opensuse.org If you'd prefer a direct contact point, the correct direct contact point would be the openSUSE admins at admin@opensuse.org Either way, this is the wrong place for this report. Everyone, please do not reply to this thread, consider it closed and offtopic. -- Richard Brown Linux Distribution Engineer - Future Technology Team SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
On 2021/09/25 10:25, Richard Brown wrote:
The correct mailinglist would be mirror@lists.opensuse.org
If you'd prefer a direct contact point, the correct direct contact point would be the openSUSE admins at admin@opensuse.org
Either way, this is the wrong place for this report. Everyone, please do not reply to this thread, consider it closed and offtopic.
---- Richard, please note, this can has happened to others who mentioned it on the users list. I may well be that mirror/admins would be more focused, but I have tried contacting the similar contacts for the kernel + kernel mirror system (twice now, once this time and once a few months ago) and _haven't_ heard back. Also, the feedback I've received on the suse side was about ways to work around the problem on a case-by-case basis -- not proposing a way to correct the problem. Furthermore, as you have noted in the past, there has been a tendency to shoot^W ignore the messenger due to 'whatever' -- sysconfig, or personal feelings... Whatever the reason, I don't want a bug-fix, but an algorithm fix as there are problems in the infrastructure that are likely to recreate similar problems in the future. I'll try to send my problems elsewhere next time and see if that helps, but if nothing is changed, it it is possible that similar conditions will arise again. I thank you for the better contact points and hope they also read this or the support list where this issue has also come up.
participants (2)
-
L A Walsh -
Richard Brown