"RPM Fusion for Fedora 41 - Nonfree - Updates" showing errors when updating

Ask Fedora
,
1

Updating via Konsole, THIS is the section I am worried about:


RPM Fusion for Fedora 41 - Nonfree - Updates                                                                       100% |  19.9 KiB/s |  39.4 KiB |  00m02s
>>> Status code: 404 for http://rpmfusion.ip-connect.vn.ua/nonfree/fedora/updates/41/x86_64/repodata/d8af8096c24330cb59da14392d26bba9f15f6693a16fd1f50bd1c2d
>>> Status code: 404 for http://ftp-stud.hs-esslingen.de/pub/Mirrors/rpmfusion.org/nonfree/fedora/updates/41/x86_64/repodata/d8af8096c24330cb59da14392d26bba
>>> Status code: 404 for https://ftp-stud.hs-esslingen.de/pub/Mirrors/rpmfusion.org/nonfree/fedora/updates/41/x86_64/repodata/d8af8096c24330cb59da14392d26bb
>>> Status code: 404 for https://mirror.netsite.dk/rpmfusion/nonfree/fedora/updates/41/x86_64/repodata/d8af8096c24330cb59da14392d26bba9f15f6693a16fd1f50bd1c
>>> Status code: 404 for http://mirror.netsite.dk/rpmfusion/nonfree/fedora/updates/41/x86_64/repodata/d8af8096c24330cb59da14392d26bba9f15f6693a16fd1f50bd1c2

I have no idea what this REALLY means (everybody knows that “404 + link” means it can’t find its whatever on the online page, I don’t know the DETAILS).
A short explanation and a way to fix this (no speculations, ACTUAL way to fix this, I’d like not to reinstall my OS because of a gaff) is what I am looking for.

Note aside: among the tags here I saw “f42” and “f43”, are these for beta testing or something??

2

This seems to be a problem with your internet connection. Can you confirm you are online? ping google.com

You could remove metadata and refresh your cache:

sudo dnf clean all
sudo dnf update

Don’t worry, we’ll fix the issue without reinstalling.

these are tags for future f42 (“branched” right now) and f43 (“rawhide” development). You can ignore them for now.

3

Thanks.
I pinged Google and it was giving me close to 1 ping per second (there was some sort of IP there so I am not pasting it).

I did le “sudo dnf clean all” and it cleaned 48 respositories, then I did a “sudo dnf update --refresh” and it was clean.

I am keeping this page open for a couple days more in case “the problem comes back” or whatever.

4

That’s an indication that your internet connection is working - also being able to post here is another one.

You could also check if DNS resolution is working fine: dig +noall +answer rpmfusion.ip-connect.vn.ua.

Anyway, I think you hit some temporary issues that are gone now.

5

I’m experiencing the same issue (error 404 and 416) but then for the standard update repo.
It comes and goes. Sometimes not a single issue for a week and then suddenly errors, try it again 3 minutes later and it goes fine.
Perhaps some of the mirrors are not the most stable ones.

6

I would read that as “some branches of the internet are not the most stable”

I seriously doubt that a server would be flaky, particularly several at the same time, but having an overloaded node on the internet that is used in the path between you and several different areas/servers is quite likely.

7

Lol this is the character for code blocks: ```

8

These are normal, and I guess that usually occur when the mirrors themselves are in the middle to be synchronized with the master version. Around here that is usually around 06:00 - 08:00 UTC time.

When dnf gets a 404 error, it will just retry with the next mirror, and
only when dnf says that all mirrors have been tried will the update fail.

3 Likes
9

I miss Windows 7…