Note that there are some explanatory texts on larger screens.

plurals
  1. POBoto S3 throws httplib.IncompleteRead occasionally
    primarykey
    data
    text
    <p>I have several daemons that read many files from Amazon S3 using boto. Once every couple of days, I'm running into a situation where an httplib.IncompleteRead is thrown out from deep inside boto. If I try and retry the request, it immediately fails with another IncompleteRead. Even if I call <code>bucket.connection.close()</code>, all further requests will still error out.</p> <p>I feel like I might've stumbled across a bug in boto here, but nobody else seems to have hit it. Am I doing something wrong? All of the daemons are single-threaded, and I've tried setting <code>is_secure</code> both ways.</p> <pre><code>Traceback (most recent call last): ... File "&lt;file_wrapper.py",&gt; line 22, in next line = self.readline() File "&lt;file_wrapper.py",&gt; line 37, in readline data = self.fh.read(self.buffer_size) File "&lt;virtualenv/lib/python2.6/site-packages/boto/s3/key.py",&gt; line 378, in read self.close() File "&lt;virtualenv/lib/python2.6/site-packages/boto/s3/key.py",&gt; line 349, in close self.resp.read() File "&lt;virtualenv/lib/python2.6/site-packages/boto/connection.py",&gt; line 411, in read self._cached_response = httplib.HTTPResponse.read(self) File "/usr/lib/python2.6/httplib.py", line 529, in read s = self._safe_read(self.length) File "/usr/lib/python2.6/httplib.py", line 621, in _safe_read raise IncompleteRead(''.join(s), amt) </code></pre> <p>Environment:</p> <ul> <li>Amazon EC2</li> <li>Ubuntu 11.10</li> <li>Python 2.6.7</li> <li>Boto 2.12.0</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload