Bug 123298 - yum does not recover gracefully after 'Connection reset by peer'
Summary: yum does not recover gracefully after 'Connection reset by peer'
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-05-16 11:12 UTC by cam
Modified: 2014-01-21 22:49 UTC (History)
0 users

Clone Of:
Last Closed: 2004-06-10 02:13:26 UTC

Attachments (Terms of Use)

Description cam 2004-05-16 11:12:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b)

Description of problem:
When connected over a wireless link to an access point and ADSL
connection, the network sometimes gives 'Connection reset by peer'
errors. Yum does not recover gracefully from these:Getting
openoffice.org-i18n-1.1.1  56% |==============           |  34 MB   
09:04 ETA Traceback (most recent call last):
  File "/usr/bin/yum", line 30, in ?
  File "/usr/share/yum/yummain.py", line 339, in main
  File "/usr/share/yum/clientStuff.py", line 1212, in download_packages
    checkfunc=(rpmUtils.checkRpmMD5, (), {'urlgraberror':1}))
  File "/usr/share/yum/clientStuff.py", line 1327, in grab
    bandwidth, conf.retries, retrycodes, checkfunc)
  File "/usr/share/yum/urlgrabber.py", line 237, in retrygrab
    progress_obj, throttle, bandwidth)
  File "/usr/share/yum/urlgrabber.py", line 343, in urlgrab
    _do_grab(filename, fo, progress_obj, raw_throttle)
  File "/usr/share/yum/urlgrabber.py", line 387, in _do_grab
    block = fo.read(bs)
  File "/usr/share/yum/keepalive.py", line 235, in read
    s = self._rbuf + self._raw_read(amt)
  File "/usr/lib/python2.3/httplib.py", line 409, in read
    s = self.fp.read(amt)
  File "/usr/lib/python2.3/socket.py", line 301, in read
    data = self._sock.recv(recv_size)
socket.error: (104, 'Connection reset by peer')

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

How reproducible:

Steps to Reproduce:
Problem is difficult to reproduce as it is triggered by low level
network conditions. However on my network it is possible to reproduce
it through any yum operation that fetches lots of rpms.

Actual Results:  yum exits with a traceback

Expected Results:  yum should clean up and retry

Additional info:

A possible workaround is to do this:

while true ; do yum -y update; done

Although it is important to check when yum is no longer updating and
ctrl-C the shell.

Comment 1 Jeff Johnson 2004-06-10 02:13:26 UTC
Graceful recovery under all possible network outages is gonna
take a bit to achieve, hence deferred.

FWIW, I see this problem on my cable modem too, so I have a
private interest in getting the problem fixed. It will happen
eventually ;-)

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