#7659 Mirrormanager is giving out EPEL mirrors which are out of date
Closed: Insufficient data 5 years ago by smooge. Opened 5 years ago by smooge.

  • Describe what you need us to do:

Got a problem listed in #epel this morning about many mirrors being given out which were 2-5 days out of date from master. This was causing 404 downloads.

Two example hosts were

http://mirror.kinamo.be/epel/7/x86_64/repodata/
https://mirrors.dotsrc.org/fedora-epel/7/x86_64/repodata/

My guess is that we are not checking them fast enough or what we are checking is coming up clean when it isn't.

  • When do you need this? (YYYY/MM/DD)

  • When is this no longer needed or useful? (YYYY/MM/DD)

  • If we cannot complete your request, what is the impact?


Both mirrors look correct right now. Difficult to say what might have gone wrong.

At the time the person was getting files like:

38a77ef82e2ab03f6691364086c643ac54a782b429c5189072ecdc1ed75e6252-primary.sqlite.bz2
065655b415212baa8ac5a69b9df2a50f9f097e9928315317eda9a29f969f5d8e-filelists.sqlite.bz2

which were older ones.

These files are also there now. Seems almost impossible to correctly understand want went wrong. Slow mirrors, wrong metalink, something else...

It is also interesting that
38a77ef82e2ab03f6691364086c643ac54a782b429c5189072ecdc1ed75e6252-primary.sqlite.bz2
is part of the latest repomd.xml
but
065655b415212baa8ac5a69b9df2a50f9f097e9928315317eda9a29f969f5d8e-filelists.sqlite.bz2
is not.

From my point of view we have to close this as I cannot debug this further. Everything I looked at seems correct.

Metadata Update from @smooge:
- Issue close_status updated to: Insufficient data
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata