BucketAlreadyOwnedByYou

What version of Boto are you using? It should be at least 0.9d. My
suspicion is that yours is a lot newer.

Also, what version of duplicity.? You can find out with 'duplicity
--version'.

Needless to say, this is a new error. I'm going to need some help
answering it.

...Ken

Max wrote:
> New question #150801 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/150801
>
> Hello,
>
> I tried to use the below script to make incremental backup with Duplicity.
>
> This is the script > http://serverfault.com/questions/31828/duplicity-and-amazon-s3-script/31878#31878.
>
> I asked around and normally this script works well.
>
> Unfortunately it doesn't work for me.
>
> This is the result I get :
>
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: none
> No old backup sets found, nothing deleted.
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: none
> Last full backup is too old, forcing full backup
> Failed to create bucket (attempt #1) 'cmsbk' failed (reason: S3CreateError: S3CreateError: 409 Conflict
> <?xml version="1.0" encoding="UTF-8"?>
> <Error><Code>BucketAlreadyOwnedByYou</Code><Message>Your previous request to create the named bucket succeeded and you already own it.</Message><BucketName>cmsbk</BucketName><RequestId>FF8B86A32CC3FE4F</RequestId><HostId>6ENGL3DT9f0n7Tkv4qdKIs/uBNCMMA6QUFapw265WmodFDluP57esOOkecp55qhh</HostId></Error>)
>
> The error message is repeated continuously since I stop it.
>
> When I stop it the below message follows
>
> Traceback (most recent call last):
> File "/usr/bin/duplicity", line 1249, in ?
> with_tempdir(main)
> File "/usr/bin/duplicity", line 1242, in with_tempdir
> fn()
> File "/usr/bin/duplicity", line 1215, in main
> full_backup(col_stats)
> File "/usr/bin/duplicity", line 417, in full_backup
> globals.backend)
> File "/usr/bin/duplicity", line 316, in write_multivol
> (tdp, dest_filename)))
> File "/usr/lib64/python2.4/site-packages/duplicity/asyncscheduler.py", line 145, in schedule_task
> return self.__run_synchronously(fn, params)
> File "/usr/lib64/python2.4/site-packages/duplicity/asyncscheduler.py", line 171, in __run_synchronously
> ret = fn(*params)
> File "/usr/bin/duplicity", line 315, in <lambda>
> async_waiters.append(io_scheduler.schedule_task(lambda tdp, dest_filename: put(tdp, dest_filename),
> File "/usr/bin/duplicity", line 241, in put
> backend.put(tdp, dest_filename)
> File "/usr/lib64/python2.4/site-packages/duplicity/backends/botobackend.py", line 165, in put
> time.sleep(30)
> KeyboardInterrupt
>
> I also tried with another similar script > https://github.com/thornomad/dt-s3-backup/blob/master/dt-s3-backup.sh
>
> but the result is always the same, it gives exactly the above error message.
>
> I tried the script on CENTOS 5.5 server.
>
> Can you help me, please ?
>
> Thanks for any help you can give
> MC
>
>

Hello,

Thank you for your reply Ken!

Here are the additional information you requested:

Boto > python-boto 1.9b-1.el5.rf (installed with yum)

boto-2.0b4 has known issue with gcc.

Duplicity version > duplicity 0.6.12

The first time I installed duplicity 0.4.11-3.el5.rf with yum, but it gave the same error so I installed

duplicity-0.6.12.tar.gz.

Thank you very much for your interest and your help.
Max

here
http://groups.google.com/group/dragonfly-users/browse_thread/thread/34dc29f9d869d039
they suggest that the creation location might be significant. maybe it points you into a direction.

ede/duply.net

On 28.03.2011 22:17, Max wrote:
> Question #150801 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/150801
>
> Status: Answered => Open
>
> Max is still having a problem:
> Hello,
>
> Thank you for your reply Ken!
>
> Here are the additional information you requested:
>
>
> Boto > python-boto 1.9b-1.el5.rf (installed with yum)
>
> boto-2.0b4 has known issue with gcc.
>
>
> Duplicity version > duplicity 0.6.12
>
> The first time I installed duplicity 0.4.11-3.el5.rf with yum, but it
> gave the same error so I installed
>
> duplicity-0.6.12.tar.gz.
>
>
> Thank you very much for your interest and your help.
> Max
>

One problem may be that duplicity is seeing older versions due to
differences in install. Please uninstall/purge the yum version of
duplicity, then reinstall the tarball and try the backup again.

Is your target an Amazon S3 instance or another S3 provider?

...Thanks,
...Ken

Max wrote:
> Question #150801 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/150801
>
> Status: Answered => Open
>
> Max is still having a problem:
> Hello,
>
> Thank you for your reply Ken!
>
> Here are the additional information you requested:
>
>
> Boto > python-boto 1.9b-1.el5.rf (installed with yum)
>
> boto-2.0b4 has known issue with gcc.
>
>
> Duplicity version > duplicity 0.6.12
>
> The first time I installed duplicity 0.4.11-3.el5.rf with yum, but it
> gave the same error so I installed
>
> duplicity-0.6.12.tar.gz.
>
>
> Thank you very much for your interest and your help.
> Max
>
>

http://john.keyes.ie/boto-create_bucket-bucketalreadyownedbyyou-error/ has
an explanation for what's happening.

I'm going to create a patch for this. Would you mind trying it out?

...Thanks,
...Ken

On Mon, Mar 28, 2011 at 3:34 PM, Kenneth Loafman <
<email address hidden>> wrote:

> Question #150801 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/150801
>
> Kenneth Loafman proposed the following answer:
> One problem may be that duplicity is seeing older versions due to
> differences in install. Please uninstall/purge the yum version of
> duplicity, then reinstall the tarball and try the backup again.
>
> Is your target an Amazon S3 instance or another S3 provider?
>
> ...Thanks,
> ...Ken
>
> Max wrote:
> > Question #150801 on Duplicity changed:
> > https://answers.launchpad.net/duplicity/+question/150801
> >
> > Status: Answered => Open
> >
> > Max is still having a problem:
> > Hello,
> >
> > Thank you for your reply Ken!
> >
> > Here are the additional information you requested:
> >
> >
> > Boto > python-boto 1.9b-1.el5.rf (installed with yum)
> >
> > boto-2.0b4 has known issue with gcc.
> >
> >
> > Duplicity version > duplicity 0.6.12
> >
> > The first time I installed duplicity 0.4.11-3.el5.rf with yum, but it
> > gave the same error so I installed
> >
> > duplicity-0.6.12.tar.gz.
> >
> >
> > Thank you very much for your interest and your help.
> > Max
> >
> >
>
> --
> You received this question notification because you are a member of
> duplicity-team, which is an answer contact for Duplicity.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help : https://help.launchpad.net/ListHelp
>

Hi,

@edso

Thanks I already knew this thread.... I checked it again but it still doesn't help unfortunately.

In addition to that I want to say that my bucket is in Northern California.

@Ken

I had already done what you suggest.

Before installing duplicity 0.6.12 tarball I uninstalled the yum version.

But the problem was still there.

I connect directly to Amazon in this way:

"DEST=s3+http://mybucket" or "s3+http://mybucket/mydir".

I also checked the link you gave..... but as I say above my bucket is in Northern California.

If duplicity creates a new bucket (in US Standard) it seems to work well.

But if I want to make backup in existing Northern California bucket it gives the error message I described.

Hope I have clearly explained.

What shall I do now ?

Thanks
Max

wait for the bugfix from ken and try it. my bet is even though you think it is a US Basket it ended up in Europe. any reason not to use the freshly created bucket to till then?

ede

Max <email address hidden> schrieb:

Question #150801 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150801 Status: Answered => Open Max is still having a problem: Hi, @edso Thanks I already knew this thread.... I checked it again but it still doesn't help unfortunately. In addition to that I want to say that my bucket is in Northern California. @Ken I had already done what you suggest. Before installing duplicity 0.6.12 tarball I uninstalled the yum version. But the problem was still there. I connect directly to Amazon in this way: "DEST=s3+http://mybucket" or "s3+http://mybucket/mydir". I also checked the link you gave..... but as I say above my bucket is in Northern California. If duplicity creates a new bucket (in US Standard) it seems to work well. But if I want to make backup in existing Northern California bucket it gives the error message I described. Hope I have clearly explained. What shall I do now ? Thanks Max -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity._____________________________________________
Mailing list: https://launchpad.net/~duplicity-team Post to : <email address hidden> Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp

Here is a patch that should fix it. It's totally untested. Let me know how
it goes.

...Ken

On Mon, Mar 28, 2011 at 5:18 PM, edso
<email address hidden>wrote:

> Question #150801 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/150801
>
> Status: Open => Answered
>
> edso proposed the following answer:
> wait for the bugfix from ken and try it. my bet is even though you think
> it is a US Basket it ended up in Europe. any reason not to use the
> freshly created bucket to till then?
>
> ede
>
>
> Max <email address hidden> schrieb:
>
> Question #150801 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/150801 Status: Answered
> => Open Max is still having a problem: Hi, @edso Thanks I already knew this
> thread.... I checked it again but it still doesn't help unfortunately. In
> addition to that I want to say that my bucket is in Northern California.
> @Ken I had already done what you suggest. Before installing duplicity 0.6.12
> tarball I uninstalled the yum version. But the problem was still there. I
> connect directly to Amazon in this way: "DEST=s3+http://mybucket" or "s3+
> http://mybucket/mydir". I also checked the link you gave..... but as I say
> above my bucket is in Northern California. If duplicity creates a new bucket
> (in US Standard) it seems to work well. But if I want to make backup in
> existing Northern California bucket it gives the error message I described.
> Hope I have clearly explained. What shall I do now ? Thanks Max -- You
> received this question notification because you are a member of
> duplicity-team, which is an answer contact for
> Duplicity._____________________________________________
> Mailing list: https://launchpad.net/~duplicity-team Post to :
> <email address hidden> Unsubscribe :
> https://launchpad.net/~duplicity-team More help :
> https://help.launchpad.net/ListHelp
>
> You received this question notification because you are a member of
> duplicity-team, which is an answer contact for Duplicity.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help : https://help.launchpad.net/ListHelp
>

Launchpad did not attach file. Here it is... https://gist.github.com/891480

...Ken

On Mon, Mar 28, 2011 at 5:42 PM, Kenneth Loafman <
<email address hidden>> wrote:

> Question #150801 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/150801
>
> Kenneth Loafman proposed the following answer:
> Here is a patch that should fix it. It's totally untested. Let me know
> how
> it goes.
>
> ...Ken
>
> On Mon, Mar 28, 2011 at 5:18 PM, edso
> <email address hidden>wrote:
>
> > Question #150801 on Duplicity changed:
> > https://answers.launchpad.net/duplicity/+question/150801
> >
> > Status: Open => Answered
> >
> > edso proposed the following answer:
> > wait for the bugfix from ken and try it. my bet is even though you think
> > it is a US Basket it ended up in Europe. any reason not to use the
> > freshly created bucket to till then?
> >
> > ede
> >
> >
> > Max <email address hidden> schrieb:
> >
> > Question #150801 on Duplicity changed:
> > https://answers.launchpad.net/duplicity/+question/150801 Status:
> Answered
> > => Open Max is still having a problem: Hi, @edso Thanks I already knew
> this
> > thread.... I checked it again but it still doesn't help unfortunately. In
> > addition to that I want to say that my bucket is in Northern California.
> > @Ken I had already done what you suggest. Before installing duplicity
> 0.6.12
> > tarball I uninstalled the yum version. But the problem was still there. I
> > connect directly to Amazon in this way: "DEST=s3+http://mybucket" or
> "s3+
> > http://mybucket/mydir". I also checked the link you gave..... but as I
> say
> > above my bucket is in Northern California. If duplicity creates a new
> bucket
> > (in US Standard) it seems to work well. But if I want to make backup in
> > existing Northern California bucket it gives the error message I
> described.
> > Hope I have clearly explained. What shall I do now ? Thanks Max -- You
> > received this question notification because you are a member of
> > duplicity-team, which is an answer contact for
> > Duplicity._____________________________________________
> > Mailing list: https://launchpad.net/~duplicity-team Post to :
> > <email address hidden> Unsubscribe :
> > https://launchpad.net/~duplicity-team More help :
> > https://help.launchpad.net/ListHelp
> >
> > You received this question notification because you are a member of
> > duplicity-team, which is an answer contact for Duplicity.
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~duplicity-team
> > Post to : <email address hidden>
> > Unsubscribe : https://launchpad.net/~duplicity-team
> > More help : https://help.launchpad.net/ListHelp
> >
>
> You received this question notification because you are a member of
> duplicity-team, which is an answer contact for Duplicity.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help : https://help.launchpad.net/ListHelp
>

Hi,

@Ken

Thank you for the patch! I appreciate your interest.

A few minutes ago I applied the patch

but..... unfortunately it gives exactly the same error.

As I say above If duplicity creates a new bucket, it is done in US Standard. In this case it seems to work well.

But I'd like to save my backup in Northern California bucket.

Is there any possibility to make Duplicity create the bucket in Northern California ?

Thanks for all
Max

In version 1.9b there are only two settings, DEFAULT and EU.
>>> from boto.s3.connection import Location
>>> dir(Location)
['DEFAULT', 'EU', '__doc__', '__module__']

Duplicity will choose EU if --s3-european-buckets is set, otherwise DEFAULT, which is US. There is no option for Northern California that I can see.

The patch I supplied should not have tried to create a new bucket at all. Please add -v9 to the duplicity command line and capture the log to a file, then paste the first 100 lines or so into your answer. Maybe that will help me see what's going on.

Hi,

Here are the first 126 lines..... and the error message.

The error message is repeated continuously since I stop it.

There is also the output displayed after I stop it.

Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Wed Mar 30 23:26:26 2011
No old backup sets found, nothing deleted.
Using archive dir: /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74
Using backup name: 7afa849886f0198cad6b2b4e2dd37c74
Import of duplicity.backends.cloudfilesbackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.OO__botobackend Succeeded
Import of duplicity.backends.botobackend Failed: the scheme s3 already has a backend associated with it
Import of duplicity.backends.sshbackend Succeeded
Import of duplicity.backends.ftpbackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.giobackend Failed: No module named gio
Import of duplicity.backends.tahoebackend Succeeded
Main action: inc
================================================================================
duplicity 0.6.12 (March 08, 2011)
Args: /usr/bin/duplicity -v9 --full-if-older-than 1M --encrypt-key=3F277453 --sign-key=517F93A7 --volsize=250 --include=/bin --include=/boot --include=/etc --include=/home --exclude=/home/b44b/vps_backups --exclude=/** / s3+http://cmsbk
Linux cmserver.cmserver.com 2.6.18-194.el5xen #1 SMP Fri Apr 2 15:34:40 EDT 2010 x86_64 x86_64
/usr/bin/python 2.4.3 (#1, Nov 11 2010, 13:30:19)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-48)]
================================================================================
Using temporary directory /tmp/duplicity-dNSAP7-tempdir
Registering (mkstemp) temporary file /tmp/duplicity-dNSAP7-tempdir/mkstemp-hnvwwa-1
Temp has 22347845632 available, backup will use approx 340787200.
Local and Remote metadata are synchronized, no sync needed.
0 files exist on backend
2 files exist in cache
Extracting backup chains from list of files: ['duplicity-full.20110331T062626Z.manifest.part', 'duplicity-full-signatures.20110331T062626Z.sigtar.part']
File duplicity-full.20110331T062626Z.manifest.part is not part of a known set; creating new set
File duplicity-full-signatures.20110331T062626Z.sigtar.part is not part of a known set; creating new set
Ignoring file (rejected by backup set) 'duplicity-full-signatures.20110331T062626Z.sigtar.part'
Found backup chain [Wed Mar 30 23:26:26 2011]-[Wed Mar 30 23:26:26 2011]
Last full backup left a partial set, restarting.
Last full backup date: Wed Mar 30 23:26:26 2011
Collection Status
-----------------
Connecting with backend: BotoBackend
Archive dir: /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74

Found 0 secondary backup chains.

Found primary backup chain with matching signature chain:
-------------------------
Chain start time: Wed Mar 30 23:26:26 2011
Chain end time: Wed Mar 30 23:26:26 2011
Number of contained backup sets: 1
Total number of contained volumes: 0
 Type of backup set: Time: Num volumes:
-------------------------
No orphaned or incomplete backup sets found.
RESTART: The first volume failed to upload before termination.
         Restart is impossible...starting backup from beginning.
BackupSet.delete: missing ['duplicity-full.20110331T062626Z.manifest.part']
Deleting /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-full.20110331T062626Z.manifest.part
Deleting /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-full-signatures.20110331T062626Z.sigtar.part
Using archive dir: /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74
Using backup name: 7afa849886f0198cad6b2b4e2dd37c74
Import of duplicity.backends.cloudfilesbackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.OO__botobackend Succeeded
Import of duplicity.backends.botobackend Failed: the scheme s3 already has a backend associated with it
Import of duplicity.backends.sshbackend Succeeded
Import of duplicity.backends.ftpbackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.giobackend Failed: No module named gio
Import of duplicity.backends.tahoebackend Succeeded
Main action: inc
================================================================================
duplicity 0.6.12 (March 08, 2011)
Args: /usr/bin/duplicity -v9 --full-if-older-than 1M --encrypt-key=3F277453 --sign-key=517F93A7 --volsize=250 --include=/bin --include=/boot --include=/etc --include=/home --exclude=/home/b44b/vps_backups --exclude=/** / s3+http://cmsbk
Linux cmserver.cmserver.com 2.6.18-194.el5xen #1 SMP Fri Apr 2 15:34:40 EDT 2010 x86_64 x86_64
/usr/bin/python 2.4.3 (#1, Nov 11 2010, 13:30:19)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-48)]
================================================================================
Using temporary directory /tmp/duplicity-yQ8P6j-tempdir
Registering (mkstemp) temporary file /tmp/duplicity-yQ8P6j-tempdir/mkstemp-kp7u8k-1
Temp has 22347841536 available, backup will use approx 340787200.
Local and Remote metadata are synchronized, no sync needed.
0 files exist on backend
0 files exist in cache
Extracting backup chains from list of files: []
Last full backup date: none
Last full backup is too old, forcing full backup
Collection Status
-----------------
Connecting with backend: BotoBackend
Archive dir: /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74

Found 0 secondary backup chains.
No backup chains with active signatures found
No orphaned or incomplete backup sets found.
Using temporary directory /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-9ul48E-tempdir
Registering (mktemp) temporary file /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-9ul48E-tempdir/mktemp-O3jKho-1
Using temporary directory /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-1NJSiS-tempdir
Registering (mktemp) temporary file /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-1NJSiS-tempdir/mktemp-FjmExz-1
AsyncScheduler: instantiating at concurrency 0
Registering (mktemp) temporary file /tmp/duplicity-yQ8P6j-tempdir/mktemp-EYowXI-2
Selecting /
Comparing () and None
Getting delta of (() / dir) and None
A .
Selecting /bin
Comparing ('bin',) and None
Getting delta of (('bin',) /bin dir) and None
A bin
Selecting /bin/arch
Comparing ('bin', 'arch') and None
Getting delta of (('bin', 'arch') /bin/arch reg) and None

...............................................................
...............................................................
...............................................................

Removing still remembered temporary file /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-9ul48E-tempdir/mktemp-O3jKho-1
Cleanup of temporary file /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-9ul48E-tempdir/mktemp-O3jKho-1 failed
Removing still remembered temporary file /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-1NJSiS-tempdir/mktemp-FjmExz-1
Cleanup of temporary file /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-1NJSiS-tempdir/mktemp-FjmExz-1 failed
AsyncScheduler: running task synchronously (asynchronicity disabled)
Failed to create bucket (attempt #1) 'cmsbk' failed (reason: S3CreateError: S3CreateError: 409 Conflict
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>BucketAlreadyOwnedByYou</Code><Message>Your previous request to create the named bucket succeeded and you already own it.</Message>
<BucketName>cmsbk</BucketName><RequestId>9518B3E9B1B1BD0C</RequestId><HostId>7dfuC/RQRcIf53RkdY17grdogAn61DiWlE5de1DtVRTnkW55t2pGq6es0sRvaGXY</HostId>
</Error>)

Removing still remembered temporary file /tmp/duplicity-yQ8P6j-tempdir/mkstemp-kp7u8k-1
Removing still remembered temporary file /tmp/duplicity-yQ8P6j-tempdir/mktemp-EYowXI-2
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1249, in ?
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1242, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1215, in main
    full_backup(col_stats)
  File "/usr/bin/duplicity", line 417, in full_backup
    globals.backend)
  File "/usr/bin/duplicity", line 316, in write_multivol
    (tdp, dest_filename)))
  File "/usr/lib64/python2.4/site-packages/duplicity/asyncscheduler.py", line 145, in schedule_task
    return self.__run_synchronously(fn, params)
  File "/usr/lib64/python2.4/site-packages/duplicity/asyncscheduler.py", line 171, in __run_synchronously
    ret = fn(*params)
  File "/usr/bin/duplicity", line 315, in <lambda>
    async_waiters.append(io_scheduler.schedule_task(lambda tdp, dest_filename: put(tdp, dest_filename),
  File "/usr/bin/duplicity", line 241, in put
    backend.put(tdp, dest_filename)
  File "/usr/lib64/python2.4/site-packages/duplicity/backends/OO__botobackend.py", line 165, in put
    time.sleep(30)
KeyboardInterrupt

Hope it helps

Thanks
Max

This may be your problem...

...
Import of duplicity.backends.OO__botobackend Succeeded
Import of duplicity.backends.botobackend Failed: the scheme s3 already has a
backend associated with it
...

If OO__botobackend is the old backend, it got imported before botobackend,
as used for S3.

...Ken

On Thu, Mar 31, 2011 at 1:54 AM, Max
<email address hidden>wrote:

> Question #150801 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/150801
>
> Status: Needs information => Open
>
> Max gave more information on the question:
> Hi,
>
> Here are the first 126 lines..... and the error message.
>
> The error message is repeated continuously since I stop it.
>
> There is also the output displayed after I stop it.
>
>
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Wed Mar 30 23:26:26 2011
> No old backup sets found, nothing deleted.
> Using archive dir:
> /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74
> Using backup name: 7afa849886f0198cad6b2b4e2dd37c74
> Import of duplicity.backends.cloudfilesbackend Succeeded
> Import of duplicity.backends.rsyncbackend Succeeded
> Import of duplicity.backends.hsibackend Succeeded
> Import of duplicity.backends.OO__botobackend Succeeded
> Import of duplicity.backends.botobackend Failed: the scheme s3 already has
> a backend associated with it
> Import of duplicity.backends.sshbackend Succeeded
> Import of duplicity.backends.ftpbackend Succeeded
> Import of duplicity.backends.webdavbackend Succeeded
> Import of duplicity.backends.imapbackend Succeeded
> Import of duplicity.backends.localbackend Succeeded
> Import of duplicity.backends.giobackend Failed: No module named gio
> Import of duplicity.backends.tahoebackend Succeeded
> Main action: inc
>
> ================================================================================
> duplicity 0.6.12 (March 08, 2011)
> Args: /usr/bin/duplicity -v9 --full-if-older-than 1M --encrypt-key=3F277453
> --sign-key=517F93A7 --volsize=250 --include=/bin --include=/boot
> --include=/etc --include=/home --exclude=/home/b44b/vps_backups
> --exclude=/** / s3+http://cmsbk
> Linux cmserver.cmserver.com 2.6.18-194.el5xen #1 SMP Fri Apr 2 15:34:40
> EDT 2010 x86_64 x86_64
> /usr/bin/python 2.4.3 (#1, Nov 11 2010, 13:30:19)
> [GCC 4.1.2 20080704 (Red Hat 4.1.2-48)]
>
> ================================================================================
> Using temporary directory /tmp/duplicity-dNSAP7-tempdir
> Registering (mkstemp) temporary file
> /tmp/duplicity-dNSAP7-tempdir/mkstemp-hnvwwa-1
> Temp has 22347845632 available, backup will use approx 340787200.
> Local and Remote metadata are synchronized, no sync needed.
> 0 files exist on backend
> 2 files exist in cache
> Extracting backup chains from list of files:
> ['duplicity-full.20110331T062626Z.manifest.part',
> 'duplicity-full-signatures.20110331T062626Z.sigtar.part']
> File duplicity-full.20110331T062626Z.manifest.part is not part of a known
> set; creating new set
> File duplicity-full-signatures.20110331T062626Z.sigtar.part is not part of
> a known set; creating new set
> Ignoring file (rejected by backup set)
> 'duplicity-full-signatures.20110331T062626Z.sigtar.part'
> Found backup chain [Wed Mar 30 23:26:26 2011]-[Wed Mar 30 23:26:26 2011]
> Last full backup left a partial set, restarting.
> Last full backup date: Wed Mar 30 23:26:26 2011
> Collection Status
> -----------------
> Connecting with backend: BotoBackend
> Archive dir: /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74
>
> Found 0 secondary backup chains.
>
> Found primary backup chain with matching signature chain:
> -------------------------
> Chain start time: Wed Mar 30 23:26:26 2011
> Chain end time: Wed Mar 30 23:26:26 2011
> Number of contained backup sets: 1
> Total number of contained volumes: 0
> Type of backup set: Time: Num volumes:
> -------------------------
> No orphaned or incomplete backup sets found.
> RESTART: The first volume failed to upload before termination.
> Restart is impossible...starting backup from beginning.
> BackupSet.delete: missing ['duplicity-full.20110331T062626Z.manifest.part']
> Deleting
> /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-full.20110331T062626Z.manifest.part
> Deleting
> /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-full-signatures.20110331T062626Z.sigtar.part
> Using archive dir:
> /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74
> Using backup name: 7afa849886f0198cad6b2b4e2dd37c74
> Import of duplicity.backends.cloudfilesbackend Succeeded
> Import of duplicity.backends.rsyncbackend Succeeded
> Import of duplicity.backends.hsibackend Succeeded
> Import of duplicity.backends.OO__botobackend Succeeded
> Import of duplicity.backends.botobackend Failed: the scheme s3 already has
> a backend associated with it
> Import of duplicity.backends.sshbackend Succeeded
> Import of duplicity.backends.ftpbackend Succeeded
> Import of duplicity.backends.webdavbackend Succeeded
> Import of duplicity.backends.imapbackend Succeeded
> Import of duplicity.backends.localbackend Succeeded
> Import of duplicity.backends.giobackend Failed: No module named gio
> Import of duplicity.backends.tahoebackend Succeeded
> Main action: inc
>
> ================================================================================
> duplicity 0.6.12 (March 08, 2011)
> Args: /usr/bin/duplicity -v9 --full-if-older-than 1M --encrypt-key=3F277453
> --sign-key=517F93A7 --volsize=250 --include=/bin --include=/boot
> --include=/etc --include=/home --exclude=/home/b44b/vps_backups
> --exclude=/** / s3+http://cmsbk
> Linux cmserver.cmserver.com 2.6.18-194.el5xen #1 SMP Fri Apr 2 15:34:40
> EDT 2010 x86_64 x86_64
> /usr/bin/python 2.4.3 (#1, Nov 11 2010, 13:30:19)
> [GCC 4.1.2 20080704 (Red Hat 4.1.2-48)]
>
> ================================================================================
> Using temporary directory /tmp/duplicity-yQ8P6j-tempdir
> Registering (mkstemp) temporary file
> /tmp/duplicity-yQ8P6j-tempdir/mkstemp-kp7u8k-1
> Temp has 22347841536 available, backup will use approx 340787200.
> Local and Remote metadata are synchronized, no sync needed.
> 0 files exist on backend
> 0 files exist in cache
> Extracting backup chains from list of files: []
> Last full backup date: none
> Last full backup is too old, forcing full backup
> Collection Status
> -----------------
> Connecting with backend: BotoBackend
> Archive dir: /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74
>
> Found 0 secondary backup chains.
> No backup chains with active signatures found
> No orphaned or incomplete backup sets found.
> Using temporary directory
> /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-9ul48E-tempdir
> Registering (mktemp) temporary file
> /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-9ul48E-tempdir/mktemp-O3jKho-1
> Using temporary directory
> /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-1NJSiS-tempdir
> Registering (mktemp) temporary file
> /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-1NJSiS-tempdir/mktemp-FjmExz-1
> AsyncScheduler: instantiating at concurrency 0
> Registering (mktemp) temporary file
> /tmp/duplicity-yQ8P6j-tempdir/mktemp-EYowXI-2
> Selecting /
> Comparing () and None
> Getting delta of (() / dir) and None
> A .
> Selecting /bin
> Comparing ('bin',) and None
> Getting delta of (('bin',) /bin dir) and None
> A bin
> Selecting /bin/arch
> Comparing ('bin', 'arch') and None
> Getting delta of (('bin', 'arch') /bin/arch reg) and None
>
> ...............................................................
> ...............................................................
> ...............................................................
>
> Removing still remembered temporary file
> /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-9ul48E-tempdir/mktemp-O3jKho-1
> Cleanup of temporary file
> /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-9ul48E-tempdir/mktemp-O3jKho-1
> failed
> Removing still remembered temporary file
> /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-1NJSiS-tempdir/mktemp-FjmExz-1
> Cleanup of temporary file
> /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-1NJSiS-tempdir/mktemp-FjmExz-1
> failed
> AsyncScheduler: running task synchronously (asynchronicity disabled)
> Failed to create bucket (attempt #1) 'cmsbk' failed (reason: S3CreateError:
> S3CreateError: 409 Conflict
> <?xml version="1.0" encoding="UTF-8"?>
> <Error><Code>BucketAlreadyOwnedByYou</Code><Message>Your previous request
> to create the named bucket succeeded and you already own it.</Message>
>
> <BucketName>cmsbk</BucketName><RequestId>9518B3E9B1B1BD0C</RequestId><HostId>7dfuC/RQRcIf53RkdY17grdogAn61DiWlE5de1DtVRTnkW55t2pGq6es0sRvaGXY</HostId>
> </Error>)
>
> Removing still remembered temporary file
> /tmp/duplicity-yQ8P6j-tempdir/mkstemp-kp7u8k-1
> Removing still remembered temporary file
> /tmp/duplicity-yQ8P6j-tempdir/mktemp-EYowXI-2
> Traceback (most recent call last):
> File "/usr/bin/duplicity", line 1249, in ?
> with_tempdir(main)
> File "/usr/bin/duplicity", line 1242, in with_tempdir
> fn()
> File "/usr/bin/duplicity", line 1215, in main
> full_backup(col_stats)
> File "/usr/bin/duplicity", line 417, in full_backup
> globals.backend)
> File "/usr/bin/duplicity", line 316, in write_multivol
> (tdp, dest_filename)))
> File "/usr/lib64/python2.4/site-packages/duplicity/asyncscheduler.py",
> line 145, in schedule_task
> return self.__run_synchronously(fn, params)
> File "/usr/lib64/python2.4/site-packages/duplicity/asyncscheduler.py",
> line 171, in __run_synchronously
> ret = fn(*params)
> File "/usr/bin/duplicity", line 315, in <lambda>
> async_waiters.append(io_scheduler.schedule_task(lambda tdp,
> dest_filename: put(tdp, dest_filename),
> File "/usr/bin/duplicity", line 241, in put
> backend.put(tdp, dest_filename)
> File
> "/usr/lib64/python2.4/site-packages/duplicity/backends/OO__botobackend.py",
> line 165, in put
> time.sleep(30)
> KeyboardInterrupt
>
> Hope it helps
>
> Thanks
> Max
>
> --
> You received this question notification because you are a member of
> duplicity-team, which is an answer contact for Duplicity.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help : https://help.launchpad.net/ListHelp
>

Hi,

Thanks for your message.

I'm little bit confused.....

Why all this happens only when I try to make a backup in Northern California bucket (empty...created by me only for this test) ?

Why all is OK when I try to make a backup in US Standard bucket (also this empty...
created by me only for this test) ?

What shall I do now ?

Shall I forget forever to have a backup in Northern California bucket (with Duplicity) ?

If so..... I'm forced to use only US Standard backup.....

Thanks
Max

Max,

If you will remove the OO_backup.py from backends, this will allow duplicity
to use the patched version which uses the existing bucket and should not try
to create a new one.

As to Northern California bucket, I don't know that such a thing exists, or
how to specify it. Currently boto does not have this capability, and
duplicity is dependent on boto for S3.

...Ken

On Fri, Apr 1, 2011 at 4:49 AM, Max <email address hidden>wrote:

> Question #150801 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/150801
>
> Status: Answered => Open
>
> Max is still having a problem:
> Hi,
>
> Thanks for your message.
>
> I'm little bit confused.....
>
> Why all this happens only when I try to make a backup in Northern
> California bucket (empty...created by me only for this test) ?
>
> Why all is OK when I try to make a backup in US Standard bucket (also this
> empty...
> created by me only for this test) ?
>
> What shall I do now ?
>
> Shall I forget forever to have a backup in Northern California bucket
> (with Duplicity) ?
>
> If so..... I'm forced to use only US Standard backup.....
>
> Thanks
> Max
>
> --
> You received this question notification because you are a member of
> duplicity-team, which is an answer contact for Duplicity.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help : https://help.launchpad.net/ListHelp
>

Max, I just came across this same issue this evening. I see the thread hasn't been updated in a while but wanted to post for anyone else that may be frustrated with this.

You can force duplicity to use the Northern California buckets (even existing ones) by editing 'connection.py' in the python modules folder (for me: /usr/lib/pymodules/python2.6/boto/s3). There are only two lines that need to be changed (->) as follows:
---------------
connection.py:91
DefaultHost = 's3.amazonaws.com' -> DefaultHost = 's3-us-west-1.amazonaws.com'

connection.py:214
 url = '%s://%s.s3.amazonaws.com/' % (http_method, bucket_name) -> url = '%s://%s.s3-us-west-1.amazonaws.com/' % (http_method, bucket_name)
---------------
If you need to use other regions (i.e. Tokyo), simply substitute with the region specific endpoints per the AWS documentation
http://aws.amazon.com/articles/3912#s3

as this is obviously official functionality this should be configurable. why don't we actually do not support to put these in the target url, maybe optionally?

..ede/duply.net

On 11.08.2011 10:36, Brandon Keszler wrote:
> Question #150801 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/150801
>
> Brandon Keszler proposed the following answer:
> Max, I just came across this same issue this evening. I see the thread
> hasn't been updated in a while but wanted to post for anyone else that
> may be frustrated with this.
>
> You can force duplicity to use the Northern California buckets (even existing ones) by editing 'connection.py' in the python modules folder (for me: /usr/lib/pymodules/python2.6/boto/s3). There are only two lines that need to be changed (->) as follows:
> ---------------
> connection.py:91
> DefaultHost = 's3.amazonaws.com' -> DefaultHost = 's3-us-west-1.amazonaws.com'
>
> connection.py:214
> url = '%s://%s.s3.amazonaws.com/' % (http_method, bucket_name) -> url = '%s://%s.s3-us-west-1.amazonaws.com/' % (http_method, bucket_name)
> ---------------
> If you need to use other regions (i.e. Tokyo), simply substitute with the region specific endpoints per the AWS documentation
> http://aws.amazon.com/articles/3912#s3
>