Description of problem:
I have multiple "fast" repos (i.e. more than 3MB/s) and one "slow" repo (30kB/s or less). I have encountered periodic timeouts during parallel download (using "dnf upgrade" command). I had to re-run the command several times until all of the packages from the fast repos downloaded and then it continued at 30kB/s for the slow repo with no more timeouts. This wasn't the first time this happened to me, so I guess there may be bug in the "detector of stalled downloads".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Fast repos with multiple (or big) updates
2. Slow repo with at least one big update
3. dnf upgrade
Timeout for the slow repo with message that there are no more mirrors to try
I think in cases there are multiple mirrors it can switch to another mirror, but in cases there are no more mirrors it should continue downloading even at the slow speed.
There was an older dnf on the machine where I encountered the problem and I will also retry with the latest dnf (as more updates accumulates to trigger the condition), but by quick scanning the changelog it doesn't seem there was anything related fixed. So that's why I am reporting it.
Related to bug 1109189, CCing Tomas.
Jaroslav, please retry with librepo-1.7.4-3 or newer and let us know if it still appears. Also, obtaining access to the slow repo would really help.
I've just talked to Jaroslav and my first guess is that downloads from fast repositories consumes majority of bandwidth and thus the download from the slow repo falls under the 1000 bytes per second for 30sec and the connection is considered too slow and aborted.
I am going to look at it more closely.
Thanks Tomas, please let us know if there is something to do on the DNF's side or feel free to move this to librepo.
Created attachment 922461 [details]
I think, this is the slow repo causing the problem. I got hardly 30kB/s in avg. in rush hour from it.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.