The duplicity-talk list has been swallowing my messages... I sent the below msg on 1/17 and tried again yesterday after realizing this. The second one didn't show up either. Can one of you forward it to the list for me? The good news is the boto developer accepted the patch.
----
Mark, it does seem to be a Tiger issue. (And FreeBSD?.) I ran into this problem today on a Mac (Tiger w/ Python 2.5 from macports), but have not seen it on Ubuntu, and it bugged me enough that I decided to dig into it this afternoon. The problem is that on some OSes, python's socket.send() throws this error simply when the send buffer is full. I might have read somewhere that this is due to these OSes creating non-blocking sockets by default.
The simple fix is to retry the send() whenever that specific exception occurs. This is the change I made to boto, and I filed the ticket [1] and uploaded the patch there. In my testing it works perfectly.
Regards,
Kevin
On Jan 25, 2008, at 11:41 AM, Darik Horn wrote:
A few weeks ago someone posted about receiving a "caught a socket error"
when trying to backup to Amazon S3 in OS X. Well, a solution never appeared,
and I'm receiving the same error.
BTW, I found a clean Mac OS X 10.4.11 computer and was able to reproduce the failure with duplicity-0.4.9, installed both locally and as a port, using either boto-0.9d or boto-1.0a.
I don't know whether the bug is in Tiger or the duplicity S3 backend.
_______________________________________________
Duplicity-talk mailing list