Bug 165055 - Yum time out makes it useless - shoudl be possible to set
Summary: Yum time out makes it useless - shoudl be possible to set
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-08-03 21:30 UTC by Adam Pribyl
Modified: 2014-01-21 22:52 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2005-08-03 21:33:10 UTC


Attachments (Terms of Use)

Description Adam Pribyl 2005-08-03 21:30:44 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.7.10) Gecko/20050717

Description of problem:
Yum fails very often with:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/x86_64/iiimf-docs-12.2-4.fc4.2.x86_64.rpm: [Errno 4] Socket Error: timed out

I've heard this is a problem of python library, however this is extremely annoying when using yum especialy on wireless networks where is lot of dropouts, laags and lost packets. Yum times out very soon - this causes either "primary.xml.gz" etc. to not be dowloaded - leads to that yum stops, or to not download header or archive leading to not finish update.


Version-Release number of selected component (if applicable):
yum-2.3.2-7

How reproducible:
Always

Steps to Reproduce:
1. Needs to have connection with higher packet loss
2. yum update
3.
  

Actual Results:  Nothing is updated, some archives are not downloaded. Yum stops.

Expected Results:  Yum does not time out so soon and tries to download as much as possible.

Additional info:

If possible there has to be a way to set up time out for yum. Mirrors are not the solution.

Comment 1 Seth Vidal 2005-08-03 21:33:10 UTC
in [main] in yum.conf

put:
timeout=45
or
timeout=60
or
timeout=3000

it's a time (in seconds)

it wasn't in the man page in 2.3.2 - it was fixed in 2.3.3 - and 2.3.4 is in
updates-testing.


Note You need to log in before you can comment on or make changes to this bug.