Just tried to update my Fedora 19 with yum check-update. It seems every mirror has a problem:
http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repo...: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror. ftp://mirror.nexicom.net/pub/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:f1f0:1:3::2: Network is unreachable" Trying other mirror.
One of the configured repositories failed (Fedora 19 - i386 - Updates), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage:
yum-config-manager --disable updates
4. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise:
yum-config-manager --save --setopt=updates.skip_if_unavailable=true
failure: repodata/repomd.xml from updates: [Errno 256] No more mirrors to try. http://fedora.mirror.nexicom.net/linux/updates/19/i386/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates
Is this temporary or should I do what Yum suggests ??
-- Your mail is being read by tight-lipped NSA agents who fail to see the humor in Doctor Strangelove.
On 12/08/13 08:03, Frank wrote:
Just tried to update my Fedora 19 with yum check-update. It seems every mirror has a problem:
http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repo...: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror. ftp://mirror.nexicom.net/pub/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:f1f0:1:3::2: Network is unreachable"
Just updated my F19 system without incident. But, I am on a IPv4 only system and you're system seems to be using IPv6. "2607:f1f0:1:3::2: Network is unreachable".
Ed Greshko Ed.Greshko@greshko.com writes:
On 12/08/13 08:03, Frank wrote:
Just tried to update my Fedora 19 with yum check-update. It seems every mirror has a problem:
http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repo...: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror. ftp://mirror.nexicom.net/pub/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:f1f0:1:3::2: Network is unreachable"
Just updated my F19 system without incident. But, I am on a IPv4 only system and you're system seems to be using IPv6. "2607:f1f0:1:3::2: Network is unreachable".
I do see that on my IPv6 systems whenever the stupid Netgear 3700v4 router craps out after 2-4 days uptime and needs a reboot. The Fedora machinery thinks IPv6 still works, but the packets never make it past the router, so every repo that advertises IPv6 connectivity fails.
-wolfgang
On 07/12/13 07:25 PM, Wolfgang S. Rupprecht wrote:
Ed Greshko Ed.Greshko@greshko.com writes:
On 12/08/13 08:03, Frank wrote:
Just tried to update my Fedora 19 with yum check-update. It seems every mirror has a problem:
http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repo...: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror. ftp://mirror.nexicom.net/pub/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:f1f0:1:3::2: Network is unreachable"
Just updated my F19 system without incident. But, I am on a IPv4 only system and you're system seems to be using IPv6. "2607:f1f0:1:3::2: Network is unreachable".
I do see that on my IPv6 systems whenever the stupid Netgear 3700v4 router craps out after 2-4 days uptime and needs a reboot. The Fedora machinery thinks IPv6 still works, but the packets never make it past the router, so every repo that advertises IPv6 connectivity fails.
-wolfgang
I don't **think** IPV6 is configured on this machine so I have no idea why YUM is trying it. Never had this problem before, then again computers are such a PITA.
Allegedly, on or about 07 December 2013, Wolfgang S. Rupprecht sent:
I do see that on my IPv6 systems whenever the stupid Netgear 3700v4 router craps out after 2-4 days uptime and needs a reboot. The Fedora machinery thinks IPv6 still works, but the packets never make it past the router
Ever tried getting Netgear to replace the faulty product? Just wondering what their response would be...
Tim ignored_mailbox@yahoo.com.au writes:
Allegedly, on or about 07 December 2013, Wolfgang S. Rupprecht sent:
I do see that on my IPv6 systems whenever the stupid Netgear 3700v4 router craps out after 2-4 days uptime and needs a reboot. The Fedora machinery thinks IPv6 still works, but the packets never make it past the router
Ever tried getting Netgear to replace the faulty product? Just wondering what their response would be...
I do like the hardware (128 MByte Dram, 128 MByte Flash). That's the highest by far that I've been able to find in a cheap $80 router. It should allow for some pretty elaborate features. I was hoping that one of the open-source firmwares (dd-wrt, open-wrt, etc) would be available for it soon.
As to getting the Netgear firmware fixed, I understand that the technical people behind the Comcast IPv6 setup are looking into the problem with Netgears. It spans the whole product line. Something goes wrong with the dhclient asking for a prefix delegation. The first one happens just fine but the renewal never happens. I suspect that Netgear is going to listen to Comcast with their millions of customers much more closely than little ol' me.
http://www.dslreports.com/forum/r28719812-IPv6-ipv6-stops-working-after-a-fe...
-wolfgang
On 07/12/13 07:08 PM, Ed Greshko wrote:
On 12/08/13 08:03, Frank wrote:
Just tried to update my Fedora 19 with yum check-update. It seems every mirror has a problem:
http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repo...: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror. ftp://mirror.nexicom.net/pub/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:f1f0:1:3::2: Network is unreachable"
Just updated my F19 system without incident. But, I am on a IPv4 only system and you're system seems to be using IPv6. "2607:f1f0:1:3::2: Network is unreachable".
That's weird because I don't think IPV6 is configured on this machine. Does YUM try that by default ? Never had this trouble before - every single mirror fails with the same error message.
On Dec 7, 2013, at 5:03 PM, Frank beacon@videotron.ca wrote:
http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repo...: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror.
I'm getting this message for pretty much every mirror on an F20 system, it seems to be an actual problem. However, dnf uses slightly different metadata and it's still working where yum fails.
Chris Murphy
On Sat, 7 Dec 2013 20:23:42 -0700, Chris Murphy wrote:
http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repo...: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror.
I'm getting this message for pretty much every mirror on an F20 system, it seems to be an actual problem. However, dnf uses slightly different metadata and it's still working where yum fails.
That's a new bug in yum-3.4.3-119 for both F19 and F20 with updates-testing. The -120 update fixes that: https://admin.fedoraproject.org/updates/search/yum
On 08/12/13 07:31 AM, Michael Schwendt wrote:
On Sat, 7 Dec 2013 20:23:42 -0700, Chris Murphy wrote:
http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repo...: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror.
I'm getting this message for pretty much every mirror on an F20 system, it seems to be an actual problem. However, dnf uses slightly different metadata and it's still working where yum fails.
That's a new bug in yum-3.4.3-119 for both F19 and F20 with updates-testing. The -120 update fixes that: https://admin.fedoraproject.org/updates/search/yum
Well that solves the problem. What I don't understand is that so few reported the difficulties. Michael you saved the day for me again ! Thanks
On 12/08/13 21:59, Frank McCormick wrote:
Well that solves the problem. What I don't understand is that so few reported the difficulties.
Well it could be that some of us never got yum-3.4.3-119 installed. Was it ever pushed to updates or was it only in updates-testing?
I updated earlier today and still have yum-3.4.3-111.fc19 installed. I can see that yum-3.4.3-120.fc19 is currently in updates-testing.
On 08/12/13 09:16 AM, Ed Greshko wrote:
On 12/08/13 21:59, Frank McCormick wrote:
Well that solves the problem. What I don't understand is that so few reported the difficulties.
Well it could be that some of us never got yum-3.4.3-119 installed. Was it ever pushed to updates or was it only in updates-testing?
I updated earlier today and still have yum-3.4.3-111.fc19 installed. I can see that yum-3.4.3-120.fc19 is currently in updates-testing.
I guess. Maybe I'll pull updates-testing from my repos - it's the 2nd time I can remember having serious problems because of it. I'll leave testing to those with a lot more experience than me.
Frank McCormick wrote:
On 08/12/13 07:31 AM, Michael Schwendt wrote:
On Sat, 7 Dec 2013 20:23:42 -0700, Chris Murphy wrote:
http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repo...: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror.
I'm getting this message for pretty much every mirror on an F20 system, it seems to be an actual problem. However, dnf uses slightly different metadata and it's still working where yum fails.
That's a new bug in yum-3.4.3-119 for both F19 and F20 with updates-testing. The -120 update fixes that: https://admin.fedoraproject.org/updates/search/yum
Well that solves the problem. What I don't understand is that so few reported the difficulties. Michael you saved the day for me again ! Thanks
May I take an educated guess? If you have no IPv6, no problem, IPv4 is used.So you never see the problem.My problem was that I do have IPv6, but got it by getting a cheap (ie. slow) connection from a 2nd ISP. So yum uses IPv6 at 1Mbit instead of IPv4 at 20Mbit. Really slow updates until I shut down IPv6 during upgrades.
HTH
-
Bill Davidsen -
Chris Murphy -
Ed Greshko -
Frank McCormick -
Michael Schwendt -
Tim -
Wolfgang S. Rupprecht