mirrors.kernel.org is a tier 1 mirror that we're currently using to mirror to mirror.facebook.net, but we're experiencing an outage because it is inconsistent (repomd.xml does not match the actual packages). Details to follow as I get more data from our internal investigation.
mirrors.kernel.org
mirror.facebook.net
Can someone verify and help get it either fixed, or remove it from Mirror Manager? Also, since the recommendation is for mirrors to pull from a tier 1 mirror, what's the mechanism for responding to this sort of outage? https://fedoraproject.org/wiki/Infrastructure/Mirroring#Mirroring
2021/03/29
@adrian do you see something on your side?
Metadata Update from @pingou: - Issue tagged with: high-gain, medium-trouble, ops
Metadata Update from @pingou: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Over the years we have seen people complaining a couple of times about mirrors.kernel.org. I guess this is related to mirrors.kernel.org being multiple machines and whenever a mirror setup tries to be clever it fails at some point.
I see mirrors.kernel.org to point to at least two systems: mirrors.pdx.kernel.org and mirrors.sfo.kernel.org. The crawler will probably only check one of the systems (I cannot check because I cannot access mirrormanager as an admin anymore).
It would probably be good to know which of the two systems syncs with the master mirror and use only that host for tier 1 access.
@salimma Probably best to use another tier 1 mirror. I cannot recommend anything else right now.
@salimma Concerning:
Can someone verify and help get it either fixed, or remove it from Mirror Manager?
Remove it from MirrorManager? Do you see problems using dnf/yum or just when you try to rsync from it? Just curious if you only see the problems while using it as tier 1 mirror via rsync. Because this is not really dependent on MirrorManager.
So, I am not sure what there is for us to do here. It would be good to know which (or both) of the mirrors is out of date and if there's problems just with rsync or also dnf... but the maintainer of that mirror is the one who should check things for being up to date and fix them.
I think in this case he was notified via email/irc...
Feel free to re-open if there's anything more we can do here.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.