duplicity-team team mailing list archive

[edso <question241395@xxxxxxxxxxxxxxxxxxxxx>]

Question #241395 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/241395

    Status: Open => Answered

edso proposed the following answer:
On 29.12.2013 20:45, Jonathan Elchison wrote:
> Question #241395 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/241395
> 
>     Status: Answered => Open
> 
> Jonathan Elchison is still having a problem:
> hi edso,
> 
> thanks for your time.  here are the requested full logs:
> 
> client (MElch2) - https://www.dropbox.com/s/vgem0zdjz6gilsy/MElch2.txt
> server (JElch4) - https://www.dropbox.com/s/2ckww3kaqfu2exe/JElch4.txt
> 
> according to the server directory listing, there is a 986M sized file
> named duplicity-full-signatures.20131227T131025Z.sigtar.gz
> 
> to see the collection-status output, search MElch2.txt for "sudo
> duplicity -v9 collection-status".  the python array printed seems to
> contain only the first 1288 objects in the directory, and the sigtar
> appears to be after this boundary.
> 


right.. the python array is shortened. the file listing ends with 'full.20131227T131025Z.vol2159.difftar.' after 1288 entries incl. the manifest.

possibly a python or paramiko bug.

please try '--ssh-backend pexpect' with '-v9' to see if it stays shortened.
if yes, 
 it's probably python try another version.
if no,
 it's paramiko. try another version or stick to pexpect.

read the manpage about ssh backend options
http://duplicity.nongnu.org/duplicity.1.html#sect16

..ede/duply.net

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.