Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=fedora-24&arch=x86_64

Hello there:
Just recently ( about 10days), we start to see
Error: Error downloading packages:
Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=fedora-24&arch=x86_64 [Connection timed out after 120001 milliseconds]

a lot, rerun most of the time solve the issue.

out environment: with docker container,
FROM fedora:24

In Dockerfile, there are multiple places running
RUN dnf -y install avahi ****

it failed at random dnf install when downloading packages.

I added ‘fastestmirror=True’ to /etc/dnf/dnf.conf
it did not help.

Since this started only about since 10 days ago, I wonder if there is any issue on mirror server side or our network side.

Thank you in advance.
LI

I wonder if this is a related discussion?

https://pagure.io/fedora-infrastructure/issue/10320

There was a comment in there about the potential for significant differences between ICMP ping timeliness and the ability of other packets to make it through, it may be interesting to see if there are any especially long paths being taken on a traceroute?

Also, completely unrelated, but I’m really personally curious if you’re able or willing to share, what is your use case for running Fedora 24 this many years later?

1 Like

I agree completely with this question. A version that has been EOL and unsupported for almost 7 years seems a bit strange for daily use and especially when connected to the internet in any way with the security issues it may have.

we are using docker container and still using Fedora 24, with python2 as default. we need to upgrade it. which version you recommend us to upgrade to with possible less impact?

For the original issue I reported, I collected traceroute
> traceroute to proxy06.fedoraproject.org (140.211.169.196), 30 hops max, 60 byte packets
>  1  gateway (172.17.0.1)  0.022 ms  0.005 ms  0.004 ms
>  2  172.16.64.1 (172.16.64.1)  0.424 ms  0.472 ms  0.558 ms
>  3  10.0.2.1 (10.0.2.1)  0.139 ms  0.122 ms  0.135 ms
>  4  12.157.149.185 (12.157.149.185)  0.527 ms  0.460 ms  0.398 ms
>  5  32.143.0.93 (32.143.0.93)  1.982 ms  1.963 ms  1.945 ms
>  6  12.240.216.42 (12.240.216.42)  9.518 ms  8.672 ms  8.558 ms
>  7  la2ca22crs.ip.att.net (12.122.2.69)  9.098 ms  9.129 ms  5.918 ms
>  8  ggr2.la2ca.ip.att.net (12.122.129.97)  5.075 ms  7.040 ms  6.068 ms
>  9  be3013.ccr41.lax05.atlas.cogentco.com (154.54.13.149)  5.820 ms  5.043 ms  5.236 ms
> 10  be3243.ccr41.lax01.atlas.cogentco.com (154.54.27.117)  5.983 ms be3359.ccr42.lax01.atlas.cogentco.com (154.54.3.69)  5.909 ms be3243.ccr41.lax01.atlas.cogentco.com (154.54.27.117)  5.950 ms
> 11  be3177.ccr22.sjc01.atlas.cogentco.com (154.54.40.146)  17.678 ms  17.319 ms  16.991 ms
> 12  be3179.ccr22.sfo01.atlas.cogentco.com (154.54.43.149)  19.699 ms  19.908 ms  20.442 ms
> 13  be3694.ccr21.pdx01.atlas.cogentco.com (154.54.84.30)  34.576 ms  34.754 ms be3693.ccr21.pdx01.atlas.cogentco.com (154.54.81.66)  36.927 ms
> 14  port-ptck-pe-02.net.linkoregon.org (207.98.127.247)  31.410 ms  32.008 ms  31.333 ms
> 15  port-ptck-pe-01.net.linkoregon.org (207.98.126.24)  32.602 ms eugn-oh-pe-02.net.linkoregon.org (207.98.126.80)  33.256 ms port-ptck-pe-01.net.linkoregon.org (207.98.126.24)  31.942 ms
> 16  corv-kerr-pe-02.net.linkoregon.org (207.98.126.89)  32.725 ms  33.155 ms  32.539 ms
> 17  corv-kerr-pe-01.net.linkoregon.org (207.98.127.242)  32.839 ms  32.209 ms  32.210 ms
> 18  proxy06.fedoraproject.org (140.211.169.196)  31.666 ms !X  32.938 ms !X  32.321 ms !X

I would say build a new container for the current version of Fedora, and then tweak to get your application to work.

we will have to upgrade the container to be latest fedora, but the challenge is the python 2 vs python3.
urgently, we need to get the current issue solved, the timeout, i just collect the traceroute:

traceroute to proxy06.fedoraproject.org (140.211.169.196), 30 hops max, 60 byte packets
1 gateway (172.17.0.1) 0.021 ms 0.008 ms 0.006 ms
2 172.16.64.1 (172.16.64.1) 0.347 ms 0.374 ms 0.428 ms
3 10.0.2.1 (10.0.2.1) 0.148 ms 0.129 ms 0.136 ms
4 12.157.149.185 (12.157.149.185) 0.418 ms 0.401 ms 0.421 ms
5 32.143.0.93 (32.143.0.93) 2.065 ms 2.045 ms 1.973 ms
6 12.240.216.42 (12.240.216.42) 6.762 ms 9.006 ms 12.386 ms
7 la2ca22crs.ip.att.net (12.122.2.69) 6.757 ms 6.780 ms 8.522 ms

sorry I can not post the rest since it has more than 2 links

it has this with *
10 be3243.ccr41.lax01.atlas.cogentco.com (154.54.27.117) 5.200 ms be3359.ccr42.lax01.atlas.cogentco.com (154.54.3.69) 5.430 ms *

and
11 * be3176.ccr21.sjc01.atlas.cogentco.com (154.54.31.190) 17.016 ms be3177.ccr22.sjc01.atlas.cogentco.com (154.54.40.146) 17.262 ms

Actually you could if it were enclosed in the Preformatted text </> tags while posting.

Note the difference between what you posted above and this copy of it with those tags.

traceroute to proxy06.fedoraproject.org (140.211.169.196), 30 hops max, 60 byte packets
1 gateway (172.17.0.1) 0.021 ms 0.008 ms 0.006 ms
2 172.16.64.1 (172.16.64.1) 0.347 ms 0.374 ms 0.428 ms
3 10.0.2.1 (10.0.2.1) 0.148 ms 0.129 ms 0.136 ms
4 12.157.149.185 (12.157.149.185) 0.418 ms 0.401 ms 0.421 ms
5 32.143.0.93 (32.143.0.93) 2.065 ms 2.045 ms 1.973 ms
6 12.240.216.42 (12.240.216.42) 6.762 ms 9.006 ms 12.386 ms
7 la2ca22crs.ip.att.net (12.122.2.69) 6.757 ms 6.780 ms 8.522 ms

Here is my traceroute

$ traceroute proxy6.fedoraproject.org
traceroute to proxy6.fedoraproject.org (140.211.169.196), 30 hops max, 60 byte packets
 1  gateway (192.168.4.1)  1.690 ms  1.774 ms  2.479 ms
 2  47.185.64.1 (47.185.64.1)  4.551 ms  15.132 ms  15.130 ms
 3  172.102.50.174 (172.102.50.174)  10.830 ms 172.102.54.64 (172.102.54.64)  15.115 ms 172.102.52.50 (172.102.52.50)  11.478 ms
 4  ae7---0.scr01.dlls.tx.frontiernet.net (74.40.3.17)  9.025 ms  9.129 ms  9.119 ms
 5  ae1---0.cbr05.dlls.tx.frontiernet.net (45.52.201.123)  9.109 ms ae0---0.cbr05.dlls.tx.frontiernet.net (45.52.201.121)  9.099 ms ae1---0.cbr05.dlls.tx.frontiernet.net (45.52.201.123)  9.090 ms
 6  equinix-dallas.transitrail.net (206.223.118.32)  12.274 ms  10.441 ms  10.416 ms
 7  fourhundredge-0-0-0-2.4079.core2.dall.net.internet2.edu (163.253.2.70)  46.955 ms  49.082 ms  50.141 ms
 8  fourhundredge-0-0-0-2.4079.core2.kans.net.internet2.edu (163.253.2.11)  50.087 ms  50.084 ms  50.077 ms
 9  fourhundredge-0-0-0-1.4079.core2.denv.net.internet2.edu (163.253.1.250)  50.103 ms  50.091 ms  50.079 ms
10  fourhundredge-0-0-0-3.4079.core2.salt.net.internet2.edu (163.253.1.169)  50.085 ms  50.066 ms  50.001 ms
11  fourhundredge-0-0-0-1.4079.core1.bois.net.internet2.edu (163.253.1.248)  49.989 ms  49.977 ms  49.964 ms
12  bois-gtwy-pe-02.net.linkoregon.org (207.98.127.223)  49.925 ms  46.625 ms  49.884 ms
13  eugn-oh-pe-02.net.linkoregon.org (207.98.126.136)  56.970 ms  56.697 ms  56.309 ms
14  port-psu-pe-02.net.linkoregon.org (207.98.126.134)  57.822 ms  57.806 ms  57.432 ms
15  corv-kerr-pe-01.net.linkoregon.org (207.98.127.242)  57.241 ms  56.730 ms  56.240 ms
16  proxy06.fedoraproject.org (140.211.169.196)  56.611 ms !X  56.208 ms !X  56.603 ms !X

traceroute shows these 2 IPs
154.54.27.117 and 154.54.31.190

they are in Africa?

As a workaround, have you tried configuring your Fedora repo in /etc/yum.repos.d/ to explicitly connect to a mirror?

Thank you Eddie, I did not know I can do that. any detail of how to do it?
I can put in something like ```
baseurl=http://

let me try it...

Yes. Instead of mirrorlist, you’ll define the baseurl.

1 Like
I did a 
cat /etc/yum.repos.d/fedora-updates.repo
[updates]
name=Fedora $releasever - $basearch - Updates
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/
metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releasever&arch=$basearch
enabled=1
gpgcheck=1
metadata_expire=6h
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

[updates-debuginfo]
name=Fedora $releasever - $basearch - Updates - Debug
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/debug/
metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-debug-f$releasever&arch=$basearch
enabled=0
gpgcheck=1
metadata_expire=6h
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

[updates-source]
name=Fedora $releasever - Updates Source
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/SRPMS/
metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-source-f$releasever&arch=$basearch
enabled=0
gpgcheck=1
metadata_expire=6h
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

all baseurl are commented out. should I just remove the #? or should the baseurl same as metalink?

You should only uncomment the baseurl for the first repo ([updates]), and comment out the metalink at the same time. None of the others are currently enabled.

It is also of note that most of the mirrors for that old a version (F24) have been closed and the baseurl should point to http://archives.fedoraproject.org/pub/archive/fedora/$releasever/$basearch/

I found a README at OCF Mirrors with that info.

ATTENTION
======================================
The contents of this directory have been moved to our archives available at:

http://archives.fedoraproject.org/pub/archive/fedora/

If you are having troubles finding something there please stop by #fedora-admin on irc.freenode.net
2 Likes