Hello,
I'm seeing issues with stale content from mirrors that are listed as being up to date at https://mirror-status.centos.org/
For example the repomd.xml file at http://mirror.it.ubc.ca/centos/7/updates/x86_64/repodata/ has not been updated since June 25, but the current file on other mirrors was updated July 16. This is not the only mirror with this problem.
I use the default mirror pool, rather than specifying a specific mirror. I became aware of this issue because I've lately been receiving dozens of messages like these everyday.
/etc/cron.hourly/0yum-hourly.cron:
Not using downloaded extras/repomd.xml because it is older than what we have: Current : Mon Jul 6 08:06:49 2020 Downloaded: Wed May 20 13:19:30 2020
On 30/07/2020 03:05, Mason Schmitt wrote:
Hello,
I'm seeing issues with stale content from mirrors that are listed as being up to date at https://mirror-status.centos.org/
Which basically checks the main root of the content dir and then displays that page. Not shown on that page is the result of the crawler process *then* only verifying *all* repositories metadata and comparing with local cache
Normally , assuming that you don't have other internal caching somewhere, it should get the list of validated (and still to be considered current) mirrors.
We've been noticing this lately on our mirrors too and we sync upstream to CentOS's primary mirrors. For example, this morning we got dozens of emails such as these:
Not using downloaded epel/repomd.xml because it is older than what we have: Current : Sun Aug 16 00:47:07 2020 Downloaded: Sat Aug 15 00:25:46 2020
Unfortunately, I don't have information on which mirror we pulled from before the time this was run but I can probably update our scripts so we can track this better. I suspect there might be an issue with one or more of the upstream mirrors not being in sync sometimes. I wonder if this is related to the other thread I started regarding centosv4.centos.org being slow for us.
On Fri, Aug 7, 2020 at 6:36 AM Fabian Arrotin arrfab@centos.org wrote:
On 30/07/2020 03:05, Mason Schmitt wrote:
Hello,
I'm seeing issues with stale content from mirrors that are listed as being up to date at https://mirror-status.centos.org/
Which basically checks the main root of the content dir and then displays that page. Not shown on that page is the result of the crawler process *then* only verifying *all* repositories metadata and comparing with local cache
Normally , assuming that you don't have other internal caching somewhere, it should get the list of validated (and still to be considered current) mirrors.
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab
CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
On 2020-08-17 18:33, Lance Albertson wrote:
We've been noticing this lately on our mirrors too and we sync upstream to CentOS's primary mirrors. For example, this morning we got dozens of emails such as these:
Not using downloaded epel/repomd.xml because it is older than what we have: Current : Sun Aug 16 00:47:07 2020 Downloaded: Sat Aug 15 00:25:46 2020
It says "epel". EPEL is provided by Fedora, not CentOS, and they have their own mirror network.
(But we got the same errors at my site as well. Our EPEL mirror pulls from mirrors.kernel.org, which was apparently stale, but they seem to have resolved their problem now. We just pulled new content from them to our mirror.)
-
Fabian Arrotin -
Lance Albertson -
Mason Schmitt -
Thomas Bellman