duplicity-team team mailing list archive

Thread
Date
Re: [Question #150801]: BucketAlreadyOwnedByYou

To: duplicity-team@xxxxxxxxxxxxxxxxxxx
From: Kenneth Loafman <question150801@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 31 Mar 2011 11:36:27 -0000
Reply-to: question150801@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx
Question #150801 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/150801

    Status: Open => Answered

Kenneth Loafman proposed the following answer:
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
<question150801@xxxxxxxxxxxxxxxxxxxxx>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     : duplicity-team@xxxxxxxxxxxxxxxxxxx
> 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.