Folks After years of working just-fine, I have an automated script that manages yum for me at initial install time. Sometime within the last 48 hours, I get the error message http://mirror.nexcess.net/epel/6/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel Trying other mirror. And this message repeats through all the mirrors, causing the load of the repomd to fail, and then the yum to fail. The resultant system becomes unusable because I need stuff from epel. I find it difficult to believe that ALL mirrors are bad, unless it's the base epel system that's failed. Does anyone have some clue? Clueless David in San Francisco
On 06/20/2015 01:17 PM, david wrote:> After years of working just-fine, I have an automated script that > manages yum for me at initial install time. Sometime within the last 48 > hours, I get the error message > > http://mirror.nexcess.net/epel/6/x86_64/repodata/repomd.xml: [Errno -1] > repomd.xml does not match metalink for epelEPEL is having network problems right now. A workaround is to comment out mirrorlist in /etc/yum.repos.d/epel.repo and add a baseurl line pointing to a known good mirror. Peter
On 20/06/15 11:21, Peter wrote:> On 06/20/2015 01:17 PM, david wrote: >> After years of working just-fine, I have an automated script that >> manages yum for me at initial install time. Sometime within the last 48 >> hours, I get the error message >> >> http://mirror.nexcess.net/epel/6/x86_64/repodata/repomd.xml: [Errno -1] >> repomd.xml does not match metalink for epel > > EPEL is having network problems right now. A workaround is to comment > out mirrorlist in /etc/yum.repos.d/epel.repo and add a baseurl line > pointing to a known good mirror. >Further, EPEL is provided by Fedora. Fedora's mirror system is currently having hiccups. http://status.fedoraproject.org/ I dropped by their admin IRC and it'd seem they have some network issues that they hope to have fixed by the end of the weekend. HTH, Pete.