Walter H. wrote:> On 23.06.2017 17:02, m.roth at 5-cent.us wrote: >> Fabian Arrotin wrote: >>> On 23/06/17 12:22, G?nther J. Niederwimmer wrote: >>>> Hello List, >>>> >>>> in the last weeks I have many, many Errors from chron hourly on my >>>> systems :- >>>> (. >>>> >>>> Have we broken or not updated mirrors in the yum config ? >>> Can you give details please ? As per design there are *no* mirrors >>> declared in the yum config files for CentOS, but they use the >>> mirrorlist >>> feature, that has all the current lists of mirrors that are >>> validated/tested in loop >> <snip> >> Missed the beginning of this - has this been for a while, or just in the >> last couple days? If so, do you have EPEL enabled? We had tons of >> errors, >> due to the error with them. Fixed by yesterday. >> > this isn't fixed ... > > yum update > Loaded plugins: fastestmirror, security > Setting up Update Process > Determining fastest mirrors > epel/metalink > | 14 kB 00:00 > * base: centos.mirror.constant.com > * epel: archive.linux.duke.edu > * extras: centos.mirror.constant.com > * updates: centos.mirror.constant.com > base > | 3.7 kB 00:00 > base/primary_db > | 4.7 MB 00:01 > epel > | 4.3 kB 00:00 > http://archive.linux.duke.edu/pub/epel/6/x86_64/repodata/repomd.xml: > [Errno -1] repomd.xml does not match metalink for epel > Trying other mirror.<snip> Hey, they've gone onto a new and different error. We were getting "not a valid .xml file. Try yum clean all, then try it. mark
On 23.06.2017 21:31, m.roth at 5-cent.us wrote:> Walter H. wrote: >> >> this isn't fixed ... >> >> yum update >> Loaded plugins: fastestmirror, security >> Setting up Update Process >> Determining fastest mirrors >> epel/metalink >> | 14 kB 00:00 >> * base: centos.mirror.constant.com >> * epel: archive.linux.duke.edu >> * extras: centos.mirror.constant.com >> * updates: centos.mirror.constant.com >> base >> | 3.7 kB 00:00 >> base/primary_db >> | 4.7 MB 00:01 >> epel >> | 4.3 kB 00:00 >> http://archive.linux.duke.edu/pub/epel/6/x86_64/repodata/repomd.xml: >> [Errno -1] repomd.xml does not match metalink for epel >> Trying other mirror. > <snip> > Hey, they've gone onto a new and different error. We were getting "not a > valid .xml file. > > Try yum clean all, then try it.this is the result after yum clean all ...
On Fri, Jun 23, 2017 at 03:31:58PM -0400, m.roth at 5-cent.us wrote:> Hey, they've gone onto a new and different error. We were getting "not a > valid .xml file. > > Try yum clean all, then try it.This post talks about what happened: http://smoogespace.blogspot.com/2017/06/problems-with-epel-and-fedora-mirroring.html (This is only the Fedora/EPEL repo issues) -- Jonathan Billings <billings at negate.org>
Jonathan Billings wrote:> On Fri, Jun 23, 2017 at 03:31:58PM -0400, m.roth at 5-cent.us wrote: >> Hey, they've gone onto a new and different error. We were getting "not a >> valid .xml file. >> >> Try yum clean all, then try it. > > This post talks about what happened: > > http://smoogespace.blogspot.com/2017/06/problems-with-epel-and-fedora-mirroring.html > > (This is only the Fedora/EPEL repo issues) >Um. yum clean all *and* yum clean metadata? Doesn't clean all include metadata? mark