Fedora updates repo metalink down?

Ask Fedora
1

It seems that the link for the meta data used for the fedora 41 updates repo is down. This causes dnf install to fail. Any info on when this link will be back online?

Fedora 41 - x86_64 - Updates                                                                                                                           0% |   0.0   B/s |   0.0   B |  00m01s
>>> Curl error (23): Failed writing received data to disk/application for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 [Failure writing output to destinat
>>> Curl error (23): Failed writing received data to disk/application for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 [Failure writing output to destinat
>>> Curl error (23): Failed writing received data to disk/application for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 [Failure writing output to destinat
>>> Librepo error: Cannot prepare internal mirrorlist: Curl error (23): Failed writing received data to disk/application for https://mirrors.fedoraproject.org/metalink?repo=updates-released-
Error checking if metalink "https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64" is in sync for repository "updates"
 Librepo error: Cannot prepare internal mirrorlist: Curl error (23): Failed writing received data to disk/application for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 [Failure writing output to destination, passed 16126 returned 0]
2

I fixed this error. It turns out that dnf install uses the /tmp directory. My /tmp directory was full so there was no space for whatever dnf install needed to store there temporarily. dnf should really give more accurate error messages. Blaming the metalink made it seem like the problem was with the metalink in /etc/yum.repos.d/fedora-updates.repo not working.

$ df -h /tmp
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           7.8G  7.8G     0 100% /tmp
1 Like
3

Please raise a bug report with your useful feedback.
See How to file a bug :: Fedora Docs

1 Like
4

I have the same issue, but my temp folder is far from being full:

$ df -h /tmp
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           6,8G   28K  6,8G   1% /tmp

So I don’t know what causes this issue on my config. Couldn’t fix it yet

5

Can you share the output of dnf that you are seeing please?

6

If /tmp is under tmpfs/RAM-backed, does that imply you don’t reboot often?

7

Here is the output:

$ sudo dnf check-update
Updating and loading repositories:
>>> Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457) - https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 - h
>>> Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457) - https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 - h
>>> Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457) - https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 - h
>>> Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457) - https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 - h
>>> Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457) - https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 - h
>>> Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457) - https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 - h
>>> Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457) - https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 - h
>>> Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457) - https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 - h
>>> Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457) - https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 - h
>>> Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457) - https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 - h
>>> Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457) - https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 - h
>>> Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457) - https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 - h
>>> Librepo error: Cannot prepare internal mirrorlist: Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457)  
Error checking if metalink "https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64" is in sync for repository "updates"
 Librepo error: Cannot prepare internal mirrorlist: Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f41&arch=x86_64 (IP: 2a05:d014:10:7803:f774:4d7c:e277:a457)
8

Maybe a problem with Fedora infrastructure. They fixed a situation like this a few days ago.
I see an issue was open a few hours ago: Issue #12541: Issues using dnf failing on 503 errors getting mirrors from 18.159.254.57 and 2a05:d014:10:7803:f774:4d7c:e277:a457 - fedora-infrastructure - Pagure.io

9

Oh, OK, thank you ! I’ll follow that