https://bugzilla.novell.com/show_bug.cgi?id=448930 User poeml@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448930#c1 Peter Poeml changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #1 from Peter Poeml 2008-11-26 01:13:59 MST --- Where are you located? Canada? The three mirrors in question (two in the US, one in Canada) all three have that file. Those are the mirrors currently listed. This is mostly all I can say for now. Until https://features.opensuse.org/?rm=feature_show&id=305320 is implemented, it is hard to diagnose these things. And until https://features.opensuse.org/index.cgi?rm=feature_show&id=302923 is implemented, it is hard to fix. Factory is a moving target and problems are to be expected more frequently in this area. A factor that contributes to this is that even though there are ideas for how to push Factory to mirrors in a better way, this isn't getting the needed attention. Lack of attention includes myself, because I am busy with other stuff of higher priority. When you let me know about specific mirrors having a problem, by writing to admin@opensuse.org, or perhaps joining the #opensuse-mirrors channel on freenode, I should be able to mostly sort it out in short term. I don't know if this an option for you. It is likely that the issue you have been seeing is due to a specific issue that one specific mirror has -- like two conflicting syncs going on. Which is something that needs to be fixed on their end, so we should let them know. If you want to help, write a script that pulls URLs like http://download.opensuse.org/factory/repo/oss/suse/noarch/xerces-j2-xml-resolver-2.8.1-238.9.noarch.rpm?mirrorlist&clientip=209.16.121.145 and checks the US mirrors if they really reply with a 200 OK status. The command curl 'http://download.opensuse.org/factory/repo/oss/suse/noarch/xerces-j2-xml-reso...' | grep 'location="\(us\|ca\)"' will give you the URLs of US and Canadian mirrors, suitable for digestion by a script. Even better, you could enhance the Python toolbox we use for monitoring for such a function: https://forgesvn1.novell.com/svn/opensuse/trunk/tools/download-redirector-v2... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=448930 User poeml@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448930#c3 --- Comment #3 from Peter Poeml 2008-11-27 13:28:22 MST --- A few hours ago, Erik came to the #opensuse-mirrors IRC channel and we debugged further issues that he had. Turns out that the GeoDNS that kernel.org deploys since a while leads to inconsistent things being seen behind the mirrors.kernel.org address we use to redirect to. This hostname resolves to mirrors.eu.kernel.org for me (and it works) and resolves to mirrors.us.kernel.org for Erik (where a file suspected to be there couldn't be found). I disabled redirections to this server for now, and I'll talk to the kernel.org admin about redirecting directly to the individual servers. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=448930 User poeml@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448930#c4 Peter Poeml changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #4 from Peter Poeml 2009-01-21 09:05:35 MST --- The issue was that kernel.org uses GeoIP-enabled DNS since a while, so that we saw different servers when scanning than our users got sent to. The issue was fixed by redirecting (and scanning) to the individual servers, thus bypassing GeoDNS. Thus, the bug was fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.