The fedora modular repo seems to be sloppy, and it looks like it chooses a wrong mirror or a badly configured mirror [CODE]dnf install *.rpm Fedora 32 openh264 (From Cisco) - x86_64 1.3 kB/s | 5.1 kB 00:03 Fedora Modular 32 - x86_64 668 kB/s | 4.9 MB 00:07 Fedora Modular 32 - x86_64 - Updates 16 kB/s | 153 kB 00:09 Errors during downloading metadata for repository 'updates-modular': - Curl error (23): Failed writing received data to disk/application for http://mirror.serverion.com/fedora/updates/32/Modular/x86_64/repodata/3ab488262465300b159446a2870437e4cf0dfb34a19741583e47cc418c55c0b7-primary.xml.zck [Failed writing body (0 != 436)] - Status code: 416 for https://nlrtm1-edge2.cdn.i3d.net/o1/k9999/pub/fedora/linux/updates/32/Modular/x86_64/repodata/3ab488262465300b159446a2870437e4cf0dfb34a19741583e47cc418c55c0b7-primary.xml.zck (IP: 109.200.196.214) - Status code: 416 for https://nlrtm1-edge2.cdn.i3d.net/o1/k9999/pub/fedora/linux/updates/32/Modular/x86_64/repodata/803d892332fc748c85a28f38c227310d2967183403fa4d0d1999618628e1b261-filelists.xml.zck (IP: 109.200.196.214) - Status code: 416 for http://nlrtm1-edge2.cdn.i3d.net/o1/k9999/pub/fedora/linux/updates/32/Modular/x86_64/repodata/803d892332fc748c85a28f38c227310d2967183403fa4d0d1999618628e1b261-filelists.xml.zck (IP: 109.200.196.214) - Curl error (23): Failed writing received data to disk/application for http://mirror.serverion.com/fedora/updates/32/Modular/x86_64/repodata/803d892332fc748c85a28f38c227310d2967183403fa4d0d1999618628e1b261-filelists.xml.zck [Failed writing body (0 != 438)] - Status code: 416 for http://nlrtm1-edge2.cdn.i3d.net/o1/k9999/pub/fedora/linux/updates/32/Modular/x86_64/repodata/3ab488262465300b159446a2870437e4cf0dfb34a19741583e47cc418c55c0b7-primary.xml.zck (IP: 109.200.196.214) Fout: Downloaden van metadata voor repo 'updates-modular' mislukte: Yum repo downloading error: Downloading error(s): repodata/3ab488262465300b159446a2870437e4cf0dfb34a19741583e47cc418c55c0b7-primary.xml.zck - Download failed: Curl error (23): Failed writing received data to disk/application for http://mirror.serverion.com/fedora/updates/32/Modular/x86_64/repodata/3ab488262465300b159446a2870437e4cf0dfb34a19741583e47cc418c55c0b7-primary.xml.zck [Failed writing body (0 != 436)]; repodata/803d892332fc748c85a28f38c227310d2967183403fa4d0d1999618628e1b261-filelists.xml.zck - Download failed: Curl error (23): Failed writing received data to disk/application for http://mirror.serverion.com/fedora/updates/32/Modular/x86_64/repodata/803d892332fc748c85a28f38c227310d2967183403fa4d0d1999618628e1b261-filelists.xml.zck [Failed writing body (0 != 438)][/CODE] When i manualy edit the fedora-updates-modular.repo and the fedora-modular.repo and change the baseurl to a specific mirror, the error's disappear. [updates-modular] name=Fedora Modular $releasever - $basearch - Updates baseurl=http://mirror.nl.leaseweb.net/fedora/linux/updates/32/Modular/x86_64/ #baseurl=http://download.example/pub/fedora/linux/updates/$releasever/Modular/$basearch/ #metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-f$releasever&arch=$basearch enabled=1 countme=1 repo_gpgcheck=0 type=rpm gpgcheck=1 metadata_expire=6h gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch skip_if_unavailable=False [fedora-modular] name=Fedora Modular $releasever - $basearch baseurl=http://mirror.nl.leaseweb.net/fedora/linux/releases/32/Modular/x86_64/os/ #baseurl=http://download.example/pub/fedora/linux/releases/$releasever/Modular/$basearch/os/ metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-$releasever&arch=$basearch enabled=1 countme=1 #metadata_expire=7d repo_gpgcheck=0 type=rpm gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch skip_if_unavailable=False after the change a dnf update gives: [CODE][root@localhost yum.repos.d]# vi fedora-updates-modular.repo [root@localhost yum.repos.d]# vi fedora-updates-modular.repo [root@localhost yum.repos.d]# dnf update Fedora Modular 32 - x86_64 - Updates 1.1 MB/s | 1.6 MB 00:01 Fedora 32 - x86_64 - Updates 786 kB/s | 10 MB 00:13 Fedora 32 - x86_64 2.3 MB/s | 70 MB 00:30 RPM Fusion for Fedora 32 - Free - Updates 279 kB/s | 206 kB 00:00 RPM Fusion for Fedora 32 - Free 103 kB/s | 679 kB 00:06 RPM Fusion for Fedora 32 - Nonfree - Updates 3.4 kB/s | 9.4 kB 00:02 RPM Fusion for Fedora 32 - Nonfree 218 kB/s | 225 kB 00:01 Afhankelijkheden opgelost. Niets te doen. Klaar! [/CODE]
Hello, can you list your versions of dnf, libdnf and librepo? Thanks!
sure, no problem. [evert@localhost ~]$ rpm -qa dnf dnf-4.2.21-1.fc32.noarch [evert@localhost ~]$ rpm -qa libdnf libdnf-0.47.0-1.fc32.x86_64 [evert@localhost ~]$ rpm -qa librepo librepo-1.11.3-1.fc32.x86_64
Thanks, Evert. We've done some fixes with regards to the error messages a while ago (in librepo-1.11.2), you've got those. Looking at this, the server is responding with 416, which is "Range Not Satisfiable". I would assume the remote repository data were damaged/inconsistent in some way. The "Failed writing body (0 != 436)" error is confusing but most likely caused by the 416. I think ideally one would expect dnf to switch to another mirror in case of such errors, but the thing is we need to download all the metadata from a single mirror to make sure they are consistent, and I think we currently can't switch to a different mirror once we start downloading from one.
Thank for your reply, Lukáš. Nothing to add for now. Feel free to close this bug.
Marking as duplicate; Not sure when we'll be to fix it though. *** This bug has been marked as a duplicate of bug 1816153 ***