Re: [Duplicity-talk] empty cache folder

[edgar . soldin]

On 25.12.2012 10:49, Druzee wrote:
>>>/ Hi,/
>>>/ /
>>>/  After uploading about 500 backup files to S3 using duplicity i can now 
>>>see /
>>>/ that the .cache/duplicity/<backupsetname> is empty./
>>>/ /
>>>/ Last time i used duplicity it did stoped responding (or so it seems) so i /
>>>/ killed it. I guess that this is somehow related, but still .../
>>>/ /
>>>/ Any suggestions on what can be done now ? duplicity wants to restart the 
>>>full /
>>>/ backup./
>>>/ /
>>
>>the cache folder is not the reason why it wants to startup a new full.
>>
>>first: use the latest release 0.6.20 .. lot's of bug fixes.
>>
>>second: what is your command line and send the output of a run with maximum 
>>verbosity (obfuscate strings you consider private) to the list or pastebin 
>>it. 
>>that should tell why it want's to start a new full.
>>
>>
>>..ede
> 
> 
> Using archive dir: /home/xxxx/.cache/duplicity/Pictures
> Using backup name: Pictures
> Import of duplicity.backends.localbackend Succeeded
> Import of duplicity.backends.webdavbackend Succeeded
> 
> Import of duplicity.backends.ftpbackend Succeeded
> Import of duplicity.backends.sshbackend Succeeded
> Import of duplicity.backends.tahoebackend Succeeded
> Import of duplicity.backends.cloudfilesbackend Succeeded
> 
> Import of duplicity.backends.ftpsbackend Succeeded
> Import of duplicity.backends.botobackend Succeeded
> Import of duplicity.backends.gdocsbackend Succeeded
> Import of duplicity.backends.hsibackend Succeeded
> Import of duplicity.backends.imapbackend Succeeded
> 
> Import of duplicity.backends.u1backend Failed: No module named httplib2
> Import of duplicity.backends.rsyncbackend Succeeded
> Main action: full
> ================================================================================
> 
> duplicity 0.6.20 (October 28, 2012)
> Args: /usr/bin/duplicity full . s3+http://bucket/yyy -v9 --name Pictures 
> --s3-unencrypted-connection
> Linux null 3.6.10-1-ARCH #1 SMP PREEMPT Tue Dec 11 09:40:17 CET 2012 x86_64 
> 
> /usr/bin/python2 2.7.3 (default, Dec 12 2012, 07:12:24) 
> [GCC 4.7.2]
> ================================================================================
> Using temporary directory /tmp/duplicity-RGLM36-tempdir
> Registering (mkstemp) temporary file 
> /tmp/duplicity-RGLM36-tempdir/mkstemp-NIyKxP-1
> 
> Temp has 2552586240 available, backup will use approx 34078720.
> Listing s3+http://bucket/yyy
> Listed s3+http://bucket/yyy/
> Listed s3+http://bucket/yyy/duplicity-full.20121217T155433Z.vol1.difftar.gpg
> 
> Listed s3+http://bucket/yyy/duplicity-full.20121217T155433Z.vol10.difftar.gpg
> Listed s3+http://bucket/yyy/duplicity-full.20121217T155433Z.vol100.difftar.gpg
> 
> Listed s3+http://bucket/yyy/duplicity-full.20121217T155433Z.vol101.difftar.gpg
> Listed s3+http://bucket/yyy/duplicity-full.20121217T155433Z.vol102.difftar.gpg
> 
> .
> <removed lines>
> .
> Listed s3+http://bucket/yyy/duplicity-full.20121217T155433Z.vol99.difftar.gpg
> Local and Remote metadata are synchronized, no sync needed.
> 
> Listing s3+http://bucket/yyy
> Listed s3+http://bucket/yyy/
> Listed s3+http://bucket/yyy/duplicity-full.20121217T155433Z.vol1.difftar.gpg
> 
> Listed s3+http://bucket/yyy/duplicity-full.20121217T155433Z.vol10.difftar.gpg
> Listed s3+http://bucket/yyy/duplicity-full.20121217T155433Z.vol100.difftar.gpg
> 
> Listed s3+http://bucket/yyy/duplicity-full.20121217T155433Z.vol101.difftar.gpg
> Listed s3+http://bucket/yyy/duplicity-full.20121217T155433Z.vol102.difftar.gpg
> 
> .
> .
> <removed lines>
> .
> Listed s3+http://bucket/yyy/duplicity-full.20121217T155433Z.vol99.difftar.gpg
> 501 files exist on backend
> 
> 0 files exist in cache
> Extracting backup chains from list of files: [u'', 
> u'duplicity-full.20121217T155433Z.vol1.difftar.gpg', 
> u'duplicity-full.20121217T155433Z.vol10.difftar.gpg', 
> .
> .
> 
> <removed lines>
> .
> full.20121217T155433Z.vol83.difftar.gpg', 
> u'duplicity-full.20121217T155433Z.vol84.difftar.gpg', 
> u'duplicity-full.20121217T155433Z.vol85.difftar.gpg', ....
> File  is not part of a known set; creating new set
> 
> Ignoring file (rejected by backup set) ''
> File duplicity-full.20121217T155433Z.vol1.difftar.gpg is not part of a known 
> set; creating new set
> File duplicity-full.20121217T155433Z.vol10.difftar.gpg is part of known set
> 
> File duplicity-full.20121217T155433Z.vol100.difftar.gpg is part of known set
> File duplicity-full.20121217T155433Z.vol101.difftar.gpg is part of known set
> File duplicity-full.20121217T155433Z.vol102.difftar.gpg is part of known set
> 
> .
> <removed lines>.
> .
> .
> File duplicity-full.20121217T155433Z.vol99.difftar.gpg is part of known set
> Warning, found incomplete backup sets, probably left from aborted session
> Last full backup date: none
> 
> Collection Status
> -----------------
> Connecting with backend: BotoBackend
> Archive dir: /home/xxxx/.cache/duplicity/Pictures
> 
> Found 0 secondary backup chains.
> No backup chains with active signatures found
> 
> Also found 0 backup sets not part of any chain,
> and 1 incomplete backup set.
> These may be deleted by running duplicity with the "cleanup" command.
> PASSPHRASE variable not set, asking user.
> PASSPHRASE variable not set, asking user.
> 
> Using temporary directory 
> /home/xxxx/.cache/duplicity/Pictures/duplicity-I6srXP-tempdir
> Registering (mktemp) temporary file 
> /home/xxxx/.cache/duplicity/Pictures/duplicity-I6srXP-tempdir/mktemp-0u6u2w-1
> Using temporary directory 
> /home/xxxx/.cache/duplicity/Pictures/duplicity-1XVkp_-tempdir
> 
> Registering (mktemp) temporary file 
> /home/xxxx/.cache/duplicity/Pictures/duplicity-1XVkp_-tempdir/mktemp-2fSWlp-1
> AsyncScheduler: instantiating at concurrency 0
> Registering (mktemp) temporary file 
> /tmp/duplicity-RGLM36-tempdir/mktemp-lJbrhu-2
> 
> Selecting .
> Comparing () and None
> Getting delta of (() . dir) and None
> A .
> Selecting ./.directory
> Comparing ('.directory',) and None
> Getting delta of (('.directory',) ./.directory reg) and None
> 
> A .directory
> Selecting ./05042011460.jpg
> Comparing ('05042011460.jpg',) and None
> Getting delta of (('05042011460.jpg',) ./05042011460.jpg reg) and None
> A 05042011460.jpg
> Selecting ./05042011461.jpg
> 
> Comparing ('05042011461.jpg',) and None
> .
> .
> .
> Removing still remembered temporary file 
> /home/xxxx/.cache/duplicity/Pictures/duplicity-I6srXP-tempdir/mktemp-0u6u2w-1
> Cleanup of temporary file 
> /home/xxxx/.cache/duplicity/Pictures/duplicity-I6srXP-tempdir/mktemp-0u6u2w-1 
> failed
> 
> Removing still remembered temporary file 
> /home/xxxx/.cache/duplicity/Pictures/duplicity-1XVkp_-tempdir/mktemp-2fSWlp-1
> Cleanup of temporary file 
> /home/xxxx/.cache/duplicity/Pictures/duplicity-1XVkp_-tempdir/mktemp-2fSWlp-1 
> failed
> 
> AsyncScheduler: running task synchronously (asynchronicity disabled)
> Uploading 
> s3+http://bucket/yyy/duplicity-full.20121225T093410Z.vol1.difftar.gpg to 
> STANDARD Storage
> 
> Removing still remembered temporary file 
> /tmp/duplicity-RGLM36-tempdir/mkstemp-NIyKxP-1
> Removing still remembered temporary file 
> /tmp/duplicity-RGLM36-tempdir/mktemp-lJbrhu-2
> INT intercepted...exiting.
> 
> Thanks !
> 

your first full is incomplete, so duplicity decides to do one. that's correct. 
usually there is also a line that tells about the decision regarding resuming. 
can't tell if you accidentially deleted it or if it's not there. please send 
the _full_ output next time.


..ede/duply.net