Re: [Duplicity-talk] S3 connection timeout

[Kenneth Loafman]

Eric Evans wrote:
> [ Greg Heartsfield ]
>> I used Duplicity for quite some time with the old bitbucket backend,
>> mostly succesfully.  Since that was switched out with boto, I've never
>> had success doing a backup to S3.  On multiple OS X (10.4/10.5)
>> machines, I get "caught a socket error, trying to recover" messages
>> from s3/key.py (as you note).
>>
>> The error is coming from boto, but I can only recreate it when boto is
>> running in the context of duplicity.  I can take backup sets created
>> with duplicity, and run a simple program that uses boto to upload them
>> to S3 without problems (most of the code is line-for-line from the
>> boto/duplicity backend).
>>
>> The error only occurs when I send data exceeding a precise number of
>> bits, which I don't have at hand at the moment, but it was something
>> like 8k (note, this is within duplicity, it works fine running only
>> boto).
>>
>> I'd also love to hear from anyone who is succesfully using
>> boto/duplicity, and what their environment is like.
> 
> I backup 5 machines (weekly full, daily incrementals) to s3 using
> duplicity. All of them are using 0.4.3 and boto 0.9b on various versions
> of Debian (stable, testing, and unstable). I can't remember the last
> time I've had a failure.

Are any of you guys that are failing on Comcast?

...Ken

signature.asc
Description: OpenPGP digital signature