Anssi Johansson kirjoitti 17.9.2017 klo 0.51:
Valeri Galtsev kirjoitti 15.9.2017 klo 20.53:
Dear All,
I have a couple of questions about one specific mirror:
Today I have multitude "package not found" errors for that mirror when updates are run on my machines. (Up to you giving up and going to different mirror). I am reluctant to point all my machines to our public mirror I maintain (I don't know why, maybe I am just lazy), and rely on fastestmirror plugin. And this keeps happening even though mirror has OK status on mirror status page:
http://mirror-status.centos.org/
My questions are:
does someone have a guess why that may be happening to me?
As my wild guess is: either that mirror starts throttling clients
badly after some amount of data, or there is some other similar reason why some stuff appears inaccessible to clients. So: could someone contact mirror maintainer with the question why someone has these problems. I am coming from domain uchicago.edu (specifically from the following IP blocks: 128.135.4.0/24, 128.135.52.0/24, 128.135.20.0/25). Or: how can I find out who the maintainer of that mirror is (I will contact the maintainer myself then)?
I noticed that http://lug.mtu.edu/centos/ redirects to http://mirrors.lug.mtu.edu/centos/ and I've now adjusted the mirror database to have the latter link. This avoids a redirect for each request, helping with any possible rate limits there might be.
As you said, mirror monitoring does not show any problems, so I tested the mirror myself by setting up a CentOS 7.3.1611 instance at UpCloud. By coincidence they have a data center in Chicago, so I got to test this from a host close to you. Obviously the routing will be different.
And at this point I found out that their http://mirrors.lug.mtu.edu/centos/7.4.1708/os/x86_64/ directory does not have a Packages subdirectory, and the same goes for the updates directory http://mirrors.lug.mtu.edu/centos/7.4.1708/updates/x86_64/
Those directories do have up-to-date repodata directories, and those are checked by the mirror checking scripts, along with the timestamps in the root directory and some files in the isos directory. The packages themselves are not checked. The timestamps seem to get updated properly, so there's something odd going on with their syncs.
I have now temporarily excluded this mirror from the mirrorlists until this issue gets resolved. I'll try contacting the mirror admins directly. Thanks for the heads up.
Looks like this has now been fixed. I have now re-enabled this mirror for the mirrorlists.