[opensuse-factory] appdata-screenshots.tar' not found on medium
HI! Trying zypper dup I get this morning: # zypper ref Repository 'openSUSE-Tumbleweed-Non-Oss' is up to date. Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata ----------------------------------------------------------------------------------------------------------------------------------[\] File '/suse/setup/descr/appdata-screenshots.tar' not found on medium 'http://download.opensuse.org/tumbleweed/repo/oss/' Ciao, Michael.
On Fri, 2017-03-17 at 09:52 +0100, Michael Ströder wrote:
HI!
Trying zypper dup I get this morning:
# zypper ref Repository 'openSUSE-Tumbleweed-Non-Oss' is up to date.
Thanks for your info - Seems we have an added complexity with Leaseeb (the only mirror currently having the file) in as they do geolocation matching on their own system - so the server WE query (system in NL) carries the patch - but their internal sync to different locations seems not completed. In what location are you? Can you please give info for:
host mirror.leaseweb.com
(mine answers with mirror.leaseweb.com is an alias for mirror.ams1.nl.leaseweb.net. mirror.ams1.nl.leaseweb.net has address 5.79.108.33 mirror.ams1.nl.leaseweb.net has IPv6 address 2001:1af8:4700:b210::33 where the file seems ok and I heard of some other user that got mirror.sfo12.us.leaseweb.net.http which did not have the file earlier, but seems to have caught up) Cheers, Dominique -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org>
Il giorno Fri, 17 Mar 2017 10:16:29 +0100 Dimstar / Dominique Leuenberger <dimstar@opensuse.org> ha scritto:
Thanks for your info - Seems we have an added complexity with Leaseeb (the only mirror currently having the file) in as they do geolocation
For the record, this can occur with many different files in different repos: this time it hit TW (but the KDE: repos were regularly affected). It's something that I already filed a ticket to admin@o.o, but it gets "solved" when a repo is updated and re-published. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2017-03-17 at 10:59 +0100, Luca Beltrame wrote:
Il giorno Fri, 17 Mar 2017 10:16:29 +0100 Dimstar / Dominique Leuenberger <dimstar@opensuse.org> ha scritto:
Thanks for your info - Seems we have an added complexity with Leaseeb (the only mirror currently having the file) in as they do geolocation
For the record, this can occur with many different files in different repos: this time it hit TW (but the KDE: repos were regularly affected). It's something that I already filed a ticket to admin@o.o, but it gets "solved" when a repo is updated and re-published.
I just posted some info on a bug, that might be interested for everybody here in the public too - the situation is 'tricky': for mirrorbrain, we have the server registered as "mirror.leaseweb.com" which 'here' resolves to: mirror.ams1.nl.leaseweb.net. and there comes the problem: LeaseWeb is not 'one server' - so even though mirrorbrain scans the 'registered' one to confirm files are in place when we redirect, that does not have to match how LeaseWeb's internal sync is complete. While debugging this together with a user over IRC, we found for example that he was redirected (by geopi dns resolution) to mirror.sfo12.us.leaseweb.net.http That's generally nice of Leaseweb, but it kills all assumptions and knowledge mirrorbrain has a) the 'location based redirection' for the server is useless: we could offer the SFO server to US users at a better prio than an NL server (this only makes a difference when there are multiple mirrors found - otherwise the NL is 'good enough' for US users) b) MirrorBrain has no information about the sync status internal at leaseweb - it only has the information about the one it can reach: which happens to be the geographically closest one in NL - and that one had the files in place at the time the users got redirected So, seems LeaseWeb found a nice way to circumvent all the logic put into MirrorBrain to not redirect to dead mirrors :( And, of course, there is a chance other CDNs will hit us in similar ways. Cheers, Dominique
Dimstar / Dominique Leuenberger wrote:
Can you please give info for:
host mirror.leaseweb.com
(mine answers with mirror.leaseweb.com is an alias for mirror.ams1.nl.leaseweb.net. mirror.ams1.nl.leaseweb.net has address 5.79.108.33 mirror.ams1.nl.leaseweb.net has IPv6 address 2001:1af8:4700:b210::33
where the file seems ok
and I heard of some other user that got mirror.sfo12.us.leaseweb.net.http which did not have the file earlier, but seems to have caught up)
all my locations (office and home in Germany): $ host mirror.leaseweb.com mirror.leaseweb.com is an alias for mirror.fra10.de.leaseweb.net. mirror.fra10.de.leaseweb.net has address 37.58.58.140 mirror.fra10.de.leaseweb.net has IPv6 address 2a00:c98:2030:a034::21 Google DNS: $ host mirror.leaseweb.com 8.8.8.8 Using domain server: Name: 8.8.8.8 Address: 8.8.8.8#53 Aliases: mirror.leaseweb.com is an alias for mirror.fra10.de.leaseweb.net. mirror.fra10.de.leaseweb.net has address 37.58.58.140 mirror.fra10.de.leaseweb.net has IPv6 address 2a00:c98:2030:a034::21 Ciao, Michael.
On Fri, 2017-03-17 at 16:31 +0100, Michael Ströder wrote:
all my locations (office and home in Germany):
$ host mirror.leaseweb.com mirror.leaseweb.com is an alias for mirror.fra10.de.leaseweb.net. mirror.fra10.de.leaseweb.net has address 37.58.58.140 mirror.fra10.de.leaseweb.net has IPv6 address 2a00:c98:2030:a034::21
Just happens to resolve to one more server - apparently also not synced (at that time) For now, Leaseweb has been disabled as an active mirror for us - this needs to be sorted out with the mirror admins directly. Cheers, Dominique
participants (3)
-
Dimstar / Dominique Leuenberger -
Luca Beltrame -
Michael Ströder