up vote 1 down vote favorite
share [g+] share [fb]

I'm trying to set up an automated backup with duplicity on Amazon S3, but I keep getting a weird error that doesn't show up on Google searches.

machina:~# duplicity --version
duplicity 0.6.14

Here is the script I'm using:

#!/bin/bash

export AWS_ACCESS_KEY_ID=????
export AWS_SECRET_ACCESS_KEY=????
export PASSPHRASE=????

duplicity --encrypt-key=A36FFD9E --sign-key DA5D5B8B --s3-european-buckets --s3-use-new-style /source/folder/ s3+http://[bucket]

export AWS_ACCESS_KEY_ID=
export AWS_SECRET_ACCESS_KEY=
export PASSPHRASE=

...and the output:

machina:~# ./backup.sh 
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
No signatures found, switching to full backup.
Upload 's3+http://[bucket]/duplicity-full.20110910T164251Z.vol1.difftar.gpg' failed (attempt #1, reason: SSLError: The write operation timed out)
Upload 's3+http://[bucket]/duplicity-full.20110910T164251Z.vol1.difftar.gpg' failed (attempt #2, reason: SSLError: The write operation timed out)
Upload 's3+http://[bucket]/duplicity-full.20110910T164251Z.vol1.difftar.gpg' failed (attempt #3, reason: SSLError: The write operation timed out)
Upload 's3+http://[bucket]/duplicity-full.20110910T164251Z.vol1.difftar.gpg' failed (attempt #4, reason: SSLError: The write operation timed out)
Upload 's3+http://[bucket]/duplicity-full.20110910T164251Z.vol1.difftar.gpg' failed (attempt #5, reason: SSLError: The write operation timed out)
Giving up trying to upload s3+http://[bucket]/duplicity-full.20110910T164251Z.vol1.difftar.gpg after 5 attempts
BackendException: Error uploading s3+http://[bucket]/duplicity-full.20110910T164251Z.vol1.difftar.gpg

I've tried running the script multiple times, to no avail. Has anyone already encountered this?

Thanks in advance !

link|improve this question
The s3+http:// url scheme only wants the bucket name, not a FQDN. – andol Sep 10 '11 at 21:08
How long have you been trying? Duplicity's manpage specifically says that European buckets take "a while before the bucket is fully accessible" and that you'll experience timeouts and errors until then. – DerfK Sep 10 '11 at 21:09
@andol: It's the same with or without the FQDN. I'll edit the post to make this clear. Derfk: I've been trying for about 6 hours. I've encountered the same problems with American buckets... – Executifs Sep 10 '11 at 21:12
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.