Hi,
It's not a first time when I experience problems with 'yum update' trying for a long time to connect to some very slow mirror. The only mirror that causes such problems for me is 'vilkam.ru', see the error below:
--- http://mirror.vilkam.ru/centos/7.2.1511/os/x86_64/repodata/c6411f1cc8a000ed2...: [Errno 14] curl#7 - "Failed connect to mirror.vilkam.ru:80; Connection refused" Trying other mirror. ---
Is there any way to notify admins of that mirror to improve its availability, or maybe remove it from the list of mirrors?
On 26/08/16 17:25, Dmitry Teselkin wrote:
Hi,
It's not a first time when I experience problems with 'yum update' trying for a long time to connect to some very slow mirror. The only mirror that causes such problems for me is 'vilkam.ru', see the error below:
http://mirror.vilkam.ru/centos/7.2.1511/os/x86_64/repodata/c6411f1cc8a000ed2...: [Errno 14] curl#7 - "Failed connect to mirror.vilkam.ru:80; Connection refused" Trying other mirror.
Is there any way to notify admins of that mirror to improve its availability, or maybe remove it from the list of mirrors?
Well, our crawler script (running in loop) validates that each mirror is reachable and also having actual content (for repodata as an example). So I verified for that host, and was able to connect to that mirror (and fetch the repodata file) from multiple locations in .US and .EU (even if it's slow)
The fact that you have "connection refused" is something else and not related to the mirror not being up2date/current : we don't know if : - you have firewall rules in place between your node and that mirror restricting outbound access - there are firewall rules on that mirror node/network that prevent some subnets to reach it
-
Dmitry Teselkin -
Fabian Arrotin