fedora-infrastructure

#11969 Running into `Errors during downloading metadata for repository 'epel'`
Closed: Fixed by phsmoura. Opened by migsaldivar.

Closed: Fixed
Reopen Issue

Describe what you would like us to do:

I'm hitting this issue when trying to install a package:

Errors during downloading metadata for repository 'epel':
  - Curl error (28): Timeout was reached for https://download-cc-rdu01.fedoraproject.org/pub/epel/8/Everything/x86_64/repodata/repomd.xml [Operation timed out after 30000 milliseconds with 0 out of 0 bytes received]
  - Curl error (28): Timeout was reached for https://download-cc-rdu01.fedoraproject.org/pub/epel/8/Everything/x86_64/repodata/91572ba2a6959bf70959598ade7ec1168bdedbf909afa6779be9cad50b20335c-prestodelta.xml.xz [Operation timed out after 30000 milliseconds with 0 out of 0 bytes received]
  - Curl error (28): Timeout was reached for https://download-cc-rdu01.fedoraproject.org/pub/epel/8/Everything/x86_64/repodata/4581d5a9ce43bbfd9a4769fb378d9450572e655cdcf3ba4c5e82bbc81f9c8ad0-filelists.xml.xz [Operation timed out after 30314 milliseconds with 0 out of 0 bytes received]
  - Curl error (28): Timeout was reached for https://download-cc-rdu01.fedoraproject.org/pub/epel/8/Everything/x86_64/repodata/783ce06abb85cc09757a9ffcb069277589dd60ee77ea194582cb6bec1f3122ea-comps-Everything.x86_64.xml.xz [Operation timed out after 30311 milliseconds with 0 out of 0 bytes received]
  - Curl error (28): Timeout was reached for https://download-cc-rdu01.fedoraproject.org/pub/epel/8/Everything/x86_64/repodata/91572ba2a6959bf70959598ade7ec1168bdedbf909afa6779be9cad50b20335c-prestodelta.xml.xz [SSL connection timeout]
Error: Failed to download metadata for repo 'epel': Yum repo downloading error: Downloading error(s): repodata/91572ba2a6959bf70959598ade7ec1168bdedbf909afa6779be9cad50b20335c-prestodelta.xml.xz - Cannot download, all mirrors were already tried without success

Are the mirrors having issues?

When do you need this to be done by? (YYYY/MM/DD)

Hum, so normally you shouldn't get that master mirror... are you using the default metalink? Or a hard coded mirror?

I corrected a few things and gave the vm more memory, but the problem seems to be rsync's are sucking up all it's disk bandwith, so http requests get delayed quite a lot.

Will ponder on some solution.

I believe it is the default, here is what dnf repolist -v prints out:

Repo-id            : epel
Repo-name          : Extra Packages for Enterprise Linux 8 - x86_64
Repo-revision      : 1717291905
Repo-updated       : Sun Jun  2 01:32:31 2024
Repo-pkgs          : 10158
Repo-available-pkgs: 10156
Repo-size          : 19 G
Repo-baseurl       : https://download.fedoraproject.org/pub/epel/8/Everything/x86_64
Repo-expire        : 172800 second(s) (last: Mon Jun  3 21:42:44 2024)
Repo-filename      : /etc/yum.repos.d/epel.repo

As well as the content of epel.repo:

root@8aa40a948f50 /# cat /etc/yum.repos.d/epel.repo
[epel]
name=Extra Packages for Enterprise Linux $releasever - $basearch
baseurl=https://download.fedoraproject.org/pub/epel/$releasever/Everything/$basearch
#metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-$releasever&arch=$basearch&infra=$infra&content=$contentdir
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8

The metalink should be default:

https://src.fedoraproject.org/rpms/epel-release/blob/epel9/f/epel.repo#_6

metalinks provide some real advantages over mirrorlists. Namely that you can't get a mirror with out of date content...

Seems its not happening anymore so closing this issue, feel free to reopen if necessary

Metadata Update from @phsmoura:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Lowest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.