Opened 16 years ago

Closed 15 years ago

Last modified 15 years ago

#14350 closed defect (invalid)

duplicity: fails to backup to S3 with "Caught a socket error, trying to recover"

Reported by: skymoo (Adam Mercer) Owned by: skymoo (Adam Mercer)
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: duplicity boto Cc: mannkind@…, simon.ree@…
Port:

Description

Duplicity fails to back up to Amazon S3 with the error:

Caught a socket error, trying to recover

Seems to be related to upsteam issue 89 (http://code.google.com/p/boto/issues/detail?id=89)

Change History (5)

comment:1 Changed 16 years ago by skymoo (Adam Mercer)

A possible fix to the problem has been found, could you apply the patch from:

http://code.google.com/p/boto/issues/detail?id=89#c9

to /opt/local/lib/python2.5/httplib.py

and see if that allows you to backup to S3?

comment:2 Changed 16 years ago by skymoo (Adam Mercer)

patch to python25 port submitted in #14802, waiting for maintainer review

comment:3 Changed 15 years ago by skymoo (Adam Mercer)

Is the problem still present with python-2.5.4, boto-1.6b, and duplicity-0.5.05?

comment:4 Changed 15 years ago by skymoo (Adam Mercer)

Resolution: invalid
Status: newclosed

No response, assuming this is not an issue with current versions.

comment:5 Changed 15 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

Note: See TracTickets for help on using tickets.