When running dnf --color=never -y upgrade --refresh -vvvvvvvvvvvvv I am getting curl timeouts with dnf on fedora32 x64. Accessing https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-32&arch=x86_64 in firefox is very quick. Please look into fixing it:
dnf --color=never -y upgrade --refresh -vvvvvvvvvvvvv
(The IP is
[shlomif@localhost ~]$ host mirrors.fedoraproject.org mirrors.fedoraproject.org is an alias for wildcard.fedoraproject.org. wildcard.fedoraproject.org has address 13.125.20.8 wildcard.fedoraproject.org has address 8.43.85.67 wildcard.fedoraproject.org has address 13.250.126.156 wildcard.fedoraproject.org has address 209.132.181.16 wildcard.fedoraproject.org has address 209.132.181.15 wildcard.fedoraproject.org has IPv6 address 2406:da18:39f:a01:35a2:d9e9:8164:a209 wildcard.fedoraproject.org has IPv6 address 2406:da12:0:c10:92a3:5a6e:221b:f9eb [shlomif@localhost ~]$
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync DNF version: 4.2.21 cachedir: /var/cache/dnf User-Agent: constructed: 'libdnf (Fedora 32; workstation; Linux.x86_64)' Copr repo for dotnet owned by @dotnet-sig 5.5 kB/s | 3.3 kB 00:00 reviving: 'copr:copr.fedorainfracloud.org:group_dotnet-sig:dotnet' can be revived - repomd matches. copr:copr.fedorainfracloud.org:group_dotnet-sig:dotnet: using metadata from Sun 26 Apr 2020 12:54:46 PM IDT. Copr repo for pamixer owned by opuk 5.4 kB/s | 3.3 kB 00:00 reviving: 'copr:copr.fedorainfracloud.org:opuk:pamixer' can be revived - repomd matches. copr:copr.fedorainfracloud.org:opuk:pamixer: using metadata from Sun 26 Apr 2020 08:52:12 AM IDT. Fedora 32 openh264 (From Cisco) - x86_64 1.1 kB/s | 986 B 00:00 reviving: 'fedora-cisco-openh264' can be revived - metalink checksums match. fedora-cisco-openh264: using metadata from Tue 17 Mar 2020 10:10:45 PM IST. countme: no event for fedora-modular: window already counted Fedora Modular 32 - x86_64 12 kB/s | 18 kB 00:01 reviving: 'fedora-modular' can be revived - metalink checksums match. fedora-modular: using metadata from Fri 24 Apr 2020 12:32:34 PM IDT. countme: no event for updates-modular: window already counted Fedora Modular 32 - x86_64 - Updates 18 kB/s | 21 kB 00:01 reviving: 'updates-modular' can be revived - metalink checksums match. updates-modular: using metadata from Sat 25 Apr 2020 07:39:30 AM IDT. countme: no event for updates-testing: window already counted Fedora 32 - x86_64 - Test Updates 19 kB/s | 16 kB 00:00 reviving: 'updates-testing' can be revived - metalink checksums match. updates-testing: using metadata from Sun 26 Apr 2020 07:02:55 AM IDT. countme: no event for updates: window already counted Fedora 32 - x86_64 - Updates 15 kB/s | 18 kB 00:01 reviving: failed for 'updates', mismatched sha256 sum. repo: downloading from remote: updates countme: no event for updates: window already counted error: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f32&arch=x86_64 [Connection timed out after 30001 milliseconds] (https://mirrors.fedoraproject.org/metalink?repo=updates-released-f32&arch=x86_64). error: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f32&arch=x86_64 [Connection timed out after 30000 milliseconds] (https://mirrors.fedoraproject.org/metalink?repo=updates-released-f32&arch=x86_64). Fedora 32 - x86_64 - Updates 6.8 kB/s | 423 kB 01:02 updates: using metadata from Sat 25 Apr 2020 04:44:51 AM IDT. countme: no event for fedora: window already counted error: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=fedora-32&arch=x86_64 [Connection timed out after 30001 milliseconds] (https://mirrors.fedoraproject.org/metalink?repo=fedora-32&arch=x86_64). error: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=fedora-32&arch=x86_64 [Connection timed out after 30001 milliseconds] (https://mirrors.fedoraproject.org/metalink?repo=fedora-32&arch=x86_64). Fedora 32 - x86_64 315 B/s | 19 kB 01:00 reviving: 'fedora' can be revived - metalink checksums match. fedora: using metadata from Fri 24 Apr 2020 02:00:23 PM IDT. RPM Fusion for Fedora 32 - Free - Updates 301 B/s | 3.1 kB 00:10 reviving: 'rpmfusion-free-updates' can be revived - metalink checksums match. rpmfusion-free-updates: using metadata from Sat 25 Apr 2020 01:02:23 PM IDT. RPM Fusion for Fedora 32 - Free 11 kB/s | 3.3 kB 00:00 reviving: 'rpmfusion-free' can be revived - metalink checksums match. rpmfusion-free: using metadata from Fri 24 Apr 2020 08:27:23 PM IDT. RPM Fusion for Fedora 32 - Nonfree - Updates 17 kB/s | 14 kB 00:00 reviving: 'rpmfusion-nonfree-updates' can be revived - metalink checksums match. rpmfusion-nonfree-updates: using metadata from Sat 25 Apr 2020 01:02:32 PM IDT. RPM Fusion for Fedora 32 - Nonfree 45 kB/s | 16 kB 00:00 reviving: 'rpmfusion-nonfree' can be revived - metalink checksums match. rpmfusion-nonfree: using metadata from Fri 24 Apr 2020 08:52:12 PM IDT. gitlab.com_paulcarroty_vscodium_repo 1.9 kB/s | 866 B 00:00 reviving: 'gitlab.com_paulcarroty_vscodium_repo' can be revived - repomd matches. gitlab.com_paulcarroty_vscodium_repo: using metadata from Sun 26 Apr 2020 06:06:43 AM IDT. Completion plugin: Generating completion cache... --> Starting dependency resolution --> Finished dependency resolution Dependencies resolved. Nothing to do. Complete!
( Reopened from https://github.com/fedora-infra/mirrormanager2/issues/283 ).
I am unable to duplicate a this time. Can you give us your ip address so we can figure out which proxy this might be happening with?
I have checked all our mirrors using this script:
#!/bin/bash PROXIES='proxy01.fedoraproject.org proxy02.fedoraproject.org proxy03.fedoraproject.org proxy04.fedoraproject.org proxy05.fedoraproject.org proxy06.fedoraproject.org proxy09.fedoraproject.or\ g proxy10.fedoraproject.org proxy11.fedoraproject.org proxy12.fedoraproject.org proxy13.fedoraproject.org proxy14.fedoraproject.org proxy30.fedoraproject.org proxy31.fedoraproject.org' URLS="https://mirrors.fedoraproject.org/metalink?repo=updates-released-f32&arch=x86_64 https://mirrors.fedoraproject.org/metalink?repo=fedora-32&arch=x86_64" for PROXY in ${PROXIES}; do for URL in ${URLS}; do echo -n "${PROXY}: " curl --connect-to mirrors.fedoraproject.org:443:${PROXY}:443 "${URL}" &> /dev/null if [[ ${?} -eq 0 ]]; then echo "mirror ${URL} is working" else echo "mirror ${URL} is not working" fi done done
They all seem to be responding correctly with no errors or timeouts.
I cut the original topic down so it can fit better in zodbot announcements.
My IP is 84.229.96.191 - ISP: Partner Communications; Tel Aviv; .il
84.229.96.191
@smooge : how do I copy+paste your bash program? when I press ctrl+a the whole issue thread page is selected and i don't have a button to view the comment's source.
When I select via mouse, and choose inside the grey it is done https://paste.centos.org/view/55c45768 will go away in 1 day
ok for some reason you are getting a proxy in Singapore and Korea and one in the US.. both of those are going to be 'long hauls'. Can you also give what host mirrors.fedoraproject.org returns. I will see if there is a problem with dns.
host mirrors.fedoraproject.org
This was already in zsh's history:
[shlomif@localhost ~]$ host mirrors.fedoraproject.org mirrors.fedoraproject.org is an alias for wildcard.fedoraproject.org. wildcard.fedoraproject.org has address 8.43.85.67 wildcard.fedoraproject.org has address 209.132.181.15 wildcard.fedoraproject.org has address 13.250.126.156 wildcard.fedoraproject.org has address 13.125.20.8 wildcard.fedoraproject.org has address 209.132.181.16 wildcard.fedoraproject.org has IPv6 address 2406:da12:0:c10:92a3:5a6e:221b:f9eb wildcard.fedoraproject.org has IPv6 address 2406:da18:39f:a01:35a2:d9e9:8164:a209 [shlomif@localhost ~]$
Thanks!
I see - not everyone can use the mouse to that effect - see "Accessibility". Thanks for the link, I started reworking it here: https://github.com/shlomif/shlomif-snippets/blob/master/check-fedora-mirrors-proxies.bash . I am getting "is working" for all of them.
OK there is a config error in our DNS mapping which is associating IL with the wrong geolocation. I am fixing and IL timeouts should be 'better' in the future.
Thanks! Please let me know when the fixed config was deployed so I can try again and confirm that the issue's symptoms are gone.
Metadata Update from @smooge: - Issue assigned to smooge
DNS now has been updated. The symptoms may still come back for other reasons. Please test.
Metadata Update from @smooge: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Thanks, @smooge ! It seems much better now here - the metadata refresh is completing in a few seconds. Feel free to close this ticket.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)