[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Duplicity-tracker] [patch #6671] s3 backend sometimes goes into perpetu
From: |
Peter Schuller |
Subject: |
[Duplicity-tracker] [patch #6671] s3 backend sometimes goes into perpetual failure |
Date: |
Wed, 12 Nov 2008 18:27:38 +0000 |
User-agent: |
Opera/9.60 (X11; FreeBSD 7.0-RELEASE-p4 amd64; U; en) Presto/2.1.1 |
URL:
<http://savannah.nongnu.org/patch/?6671>
Summary: s3 backend sometimes goes into perpetual failure
Project: duplicity
Submitted by: scode
Submitted on: Wed 12 Nov 2008 06:27:36 PM GMT
Category: None
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
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:
<http://savannah.nongnu.org/patch/?6671>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [Duplicity-tracker] [patch #6671] s3 backend sometimes goes into perpetual failure,
Peter Schuller <=