[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Duplicity-tracker] [bug #25100] s3 backend sometimes goes into perpetua

From: Kenneth Loafman
Subject: [Duplicity-tracker] [bug #25100] s3 backend sometimes goes into perpetual failure
Date: Mon, 15 Dec 2008 12:23:37 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/2008111317 Ubuntu/8.04 (hardy) Firefox/3.0.4


                 Summary: s3 backend sometimes goes into perpetual failure
                 Project: duplicity
            Submitted by: scode
            Submitted on: Mon 15 Dec 2008 06:23:36 AM CST
                Category: None
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any



I have had difficulty making large backups to the s3 backend, possible only
to european buckets (I do not know whether the timing of the problem is a
co-incidence or not).

After finally triggering this with proper error reporting, I see:

" failed (attempt #64, reason: CannotSendRequest: )"

The CannotSendRequest exception comes from Python's httplib (unfortunately
constructed without additional details). It does this if the connection is not
internally considered to be in IDLE state.

The s3 backend re-uses an S3Connection. This is fine, but the above is
probably an underlying problem with boto.

I'll try to investigate whether I can see what's going on in S3, and
otherwise confirm that not re-using the S3Connection fixes this. For now, I
wanted to file the problem.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]