dnf failed to download repomd.xml from updates

[jd1008]

On 05/28/2015 09:23 AM, Terry Polzin wrote:
>
> On Thu, May 28, 2015 at 11:21 AM, Patrick O'Callaghan 
> <pocallaghan at gmail.com <mailto:pocallaghan at gmail.com>> wrote:
>
>     On Thu, 2015-05-28 at 08:25 -0400, Radek Holy wrote:
>     >
>     > ----- Original Message -----
>     > > From: "jd1008" <jd1008 at gmail.com <mailto:jd1008 at gmail.com>>
>     > > To: "Fedora Community Users Support"
>     <users at lists.fedoraproject.org <mailto:users at lists.fedoraproject.org>
>     > > >
>     > > Sent: Thursday, May 28, 2015 12:11:34 AM
>     > > Subject: dnf failed to download repomd.xml from updates
>     > >
>     > > # dnf distro-sync
>     > > Fedora 22 - x86_64 3.1 MB/s |  41 MB     00:13
>     > > RPM Fusion for Fedora 22 - Free -
>     > > Updates    1.1 kB/s |
>     > > 399
>     > > B     00:00
>     > > RPM Fusion for Fedora 22 - Nonfree -
>     > > Updates 2.8 kB/s | 399
>     > >  B
>     > > 00:00
>     > > RPM Fusion for Fedora 22 -
>     > > Free            955
>     > > kB/s |
>     > > 551 kB     00:00
>     > > Error: Failed to synchronize cache for repo 'updates' from
>     > > 'https://mirrors.fedoraproject.org/metalink?repo=updates-released
>     > > -f22&arch=x86_64':
>     > > Cannot download repomd.xml: Curl error (56): Failure when
>     receiving
>     > > data
>     > > from the peer for
>     > > ftp://mirror.lstn.net/fedora/updates/22/x86_64/repodata/repomd.xml
>     > > [response reading failed]
>     >
>     > I guess that this is the same as
>     > https://bugzilla.redhat.com/show_bug.cgi?id=1220269 even though it
>     > happened at another time.
>
>     I'm getting repeated failures of this type:
>
>     Failure when receiving data from the peer for
>     ftp://ftp.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/development/22/x86_64/os/Packages/k/kde-l10n-14.12.3-6.fc22.noarch.rpm
>     [response reading failed]
>
>     I get the same even after "dnf clean all", and it happens with update,
>     install, distro-sync, ...
>
>
>
>
> 64-bit issue?  I've had no issues with 32-bit. 
I do not think it is a 'bitness' issue. I think it is a recurring issue with
every new release. Packages that are well and good in previous release
are not all recompiled for the new release and placed in the repos.
Also, during the first week or two of a new release, the servers are
extremely busy being updated, and they are not able to respond
quickly enough to the clients, and the clients time out and declare
their inability to download something.