Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1185553 - dnf: connection timeout is too high
Summary: dnf: connection timeout is too high
Keywords:
Status: CLOSED DUPLICATE of bug 1175466
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-24 16:11 UTC by Zbigniew Jędrzejewski-Szmek
Modified: 2015-01-26 11:21 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-26 11:21:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Zbigniew Jędrzejewski-Szmek 2015-01-24 16:11:32 UTC 
Description of problem:
Sometimes dnf cannot connect to a mirror. After some time it tries with the next mirror, after printing something like "Connection timed out after 120001 milliseconds". A timeout of 120s for a connection is just too big. If a connection to a server does not succeed in 1s it probably isn't worth using it anyway. I think a timeout of 3s would be suitable and reduce the pain caused by non-responsive mirrors.

[MIRROR] colord-libs-1.2.8-1.fc22.x86_64.rpm: Curl error: Timeout was reached for ftp://mirrors.zimcom.net/pub/fedora/linux/development/rawhide/x86_64/os/Packages/c/colord-libs-1.2.8-1.fc22.x86_64.rpm [Connection timed out after 120001 milliseconds]

Version-Release number of selected component (if applicable):
dnf-0.6.3-3.fc22.noarch
Comment 1 Honza Silhan 2015-01-26 11:21:07 UTC 
Hi, it will be configurable.

*** This bug has been marked as a duplicate of bug 1175466 ***
Note You need to log in before you can comment on or make changes to this bug.