503 errors when dowloading updates via distro-sync

Hi all. This is my first post here. Apologies if this is not the right place to post.

I’m relatively new to Linux, and I’m new to Fedora. I installed the Fedora 43, xfce spin, a couple of weeks ago. I haven’t run into major issues so far, but I ran sudo dnf distro-sync earlier today and found the following 503 errors:

I’m based in Western Europe. It seems the installation for these entries was cancelled mid way, while others just ran as expected. I received a Completed! exit code. Is this behaviour to be expected, and should I do something afterwards?

Thank you.

It looks like DNF has tried to contact Yandex, (as DNF calculated it would be the best mirror).
The connection to Yandex was refused or terminated, and then DNF connected to another mirror, which was successful.
Nothing to worry about.

3 Likes

I saw another post on the weekend of someone having issues (wrong checksums) with yandex. So, this seems to be a mirror problem…

You can limit the countries in which mirrors are being tried. I am in Western Europe too, and modified the metalink link in my .repo as following:

metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch&country=DE,FR,BE,CH,NL,SE,US
2 Likes

The installation shouldn’t have been cancelled midway - DNF works transactionally, the transaction either completely succeeds or completely fails.

If you got a “Completed” exit code, then the operation should have been successful (whatever got a 503 subsequently succeeded on retry).

What does dnf history info last tell you? Did the new versions get installed?

3 Likes

Thank you all. Indeed, it seems the installations went through and the newer versions replaced earlier ones. Another distro-sync didn’t find any missing or pending updates.
I will review the .repo next, looks like an interesting choice.

1 Like

You will have to do this manually for all Fedora repos enabled (like fedora.repo and fedora-updates.repo)