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 ?
Thanks for a answer,
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 ?
Thanks for a answer,
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
The only exception to that is for AltArch, like aarch64,armhfp,ppc64{le} arches, which are just pointing directly to mirror.centos.org
Or maybe you're talking about *non* CentOS mirrors but rather third-party mirrors ?
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.
mark
On 23.06.2017 17:02, m.roth@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. epel | 4.3 kB 00:00 http://fedora-epel.mirrors.tds.net/fedora-epel/6/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel Trying other mirror. epel | 4.2 kB 00:00 epel/primary_db | 5.9 MB 00:03 extras | 3.4 kB 00:00 extras/primary_db | 29 kB 00:00 updates | 3.4 kB 00:00 updates/primary_db | 2.0 MB 00:00 No Packages marked for Update
Walter H. wrote:
On 23.06.2017 17:02, m.roth@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@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@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-mirror...
(This is only the Fedora/EPEL repo issues)
Jonathan Billings wrote:
On Fri, Jun 23, 2017 at 03:31:58PM -0400, m.roth@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-mirror...
(This is only the Fedora/EPEL repo issues)
Um. yum clean all *and* yum clean metadata? Doesn't clean all include metadata?
mark
El 26/6/17 a las 22:13, m.roth@5-cent.us escribió:
Um. yum clean all *and* yum clean metadata? Doesn't clean all include metadata?
mark
Yes, it does. See Table 8.3 here https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/htm...
------------ Original Message ------------
Date: Monday, June 26, 2017 16:13:02 -0400 From: m.roth@5-cent.us
Jonathan Billings wrote:
On Fri, Jun 23, 2017 at 03:31:58PM -0400, m.roth@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-fed ora-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
... and the article says:
The client side fixes are currently to do *either* one of the following ...
acknowledging that point.
On 06/23/2017 05:22 AM, 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 ?
Thanks for a answer,
Another possibility is just the timing. When we release a CentOS update to mirror.centos.org, we release it to a master mirror and that takes it to other mirror.centos.org mirrors. That process takes about 30 minutes.
External mirrors, which sync at their own choosing, then get that content on their schedule.
We have a mirrorlist that gets populated by both mirror.centos.org and external servers. That list takes some time to generate and there is some lag time from when release updates and they are available everywhere.
During that lag time, you can get yum errors. Usually, a yum clear all and then a rerun of yum will fix the issues.
In the last several days we have had updates every day.
Am Freitag, 23. Juni 2017, 12:22:25 CEST schrieb Günther J. Niederwimmer:
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 ?
Thanks for a answer,
The answer
yum clean metadata
is helping me ;-)
Thanks!