Re: [Duplicity-talk] duplicity +par2 hangs (or so it seems)

[edgar . soldin]

Harry,

1. out of interest, why did you use pexpect ssh backend and not default 
paramiko?

2. might be a bug. can you try if adding --ssh-askpass helps with 
pexpect+scp:// ?

enabling debug verbosity (-v9) might give more details to the log what the 
pexpect backend is doing in the background. 

..ede/duply.net

On 14.05.2017 01:35, harry via Duplicity-talk wrote:
> It looks like the scp command failed to include the destiny's
> password, so first I tried to replace 'scp' with 'ssh', which 
> he didn't accept:
> UnsupportedBackendScheme: scheme not supported in url: 
> pexpect+ssh://<destiny>:<password>@...
> 
> So then I switched to sftp and that works now. 
> Problem solved. Just for the record.
> 
> Harry
> 
> 
> 
> On Sat, 13 May 2017 22:48:07 +0000
> harry via Duplicity-talk <address@hidden> wrote:
> 
>> It seems that for some reason scp isn't working. I did a listing of
>> the duplicity processes:
>>
>>
>>
>> address@hidden duplicity-0.7.12]$ ps aux|grep duplicity
>>
>> avahi      597  0.0  0.1  27900  1224 ?        Ss   May12   0:00
>> avahi-daemon: running [duplicity-test.local] 
>>
>> user      4768  0.0  0.3 115384  3400 pts/0    S+   09:29   0:00
>> python2 /bin/duplicity --tempdir=/home/user/.temp /rw
>> par2+pexpect+scp://pi:address@hidden//media/backupdrive/backup/duplicity/test1/rw
>>
>> user     16066  0.0  0.2  73608  2384 pts/5    Ss+  22:33
>> 0:00 /bin/scp -oServerAliveInterval=15
>> -oServerAliveCountMax=2 
>> /home/user/.temp/duplicity-uEnOe4-tempdir/mktemp-z2UoWG-2
>> address@hidden:/media/backupdrive/backup/duplicity/test1/rw/duplicity-full.20170513T223303Z.vol1.difftar.gpg
>>
>> user     16067  0.0  0.3  76196  3640 pts/5    S+   22:33
>> 0:00 /usr/bin/ssh -x -oForwardAgent=no -oPermitLocalCommand=no
>> -oClearAllForwardings=yes -o ServerAliveInterval=15
>> -oServerAliveCountMax=2 -l pi -- 192.168.2.200 scp
>> -t 
>> /media/backupdrive/backup/duplicity/test1/rw/duplicity-full.20170513T223303Z.vol1.difftar.gpg
>>
>> user     16076  0.0  0.0 109180   900 pts/1    S+   22:35   0:00 grep
>> --color=auto duplicity 
>>
>> address@hidden duplicity-0.7.12]$ ls
>> -l /home/user/.temp/duplicity-uEnOe4-tempdir/mktemp-z2UoWG-2
>>  -rw------- 1 user user 209753903 May 13
>> 22:33 /home/user/.temp/duplicity-uEnOe4-tempdir/mktemp-z2UoWG-2
>>
>> address@hidden duplicity-0.7.12]$
>>
>>
>>
>>
>> So, to me it looks like it's trying to send a file via scp, but when I
>> look at the destination computer, then there's no file at all in the
>> specified directory:
>>
>>
>> address@hidden:/media/backupdrive/backup/duplicity/test1/rw $ ls -l
>> total 0
>> address@hidden:/media/backupdrive/backup/duplicity/test1/rw $
>>
>>
>> This has worked in my old duplicity however.
>>
>> Harry
>>
>>
>> On Sat, 13 May 2017 20:32:49 +0000
>> harry via Duplicity-talk <address@hidden> wrote:
>>
>>> So I installed duplicity from the newest source, installed par2,
>>> and am now testing it on a virtual machine. The command line
>>> command is:
>>>
>>> $ duplicity /source
>>> par2+pexpect+scp://<user>:<pass>@<ip>//<destination>
>>>
>>> and it was started some 10 hours ago (09:49 on May 13th). 
>>> (It's now 20:30) Since then it has created some
>>> duplicity-??????-tempdir instances in its temp dir in which some 
>>> contain what seems to be a simlink to a file
>>> duplicity-full.20170513T103013Z.vol1.difftar.gpg
>>>
>>> Those links look like:
>>>
>>> duplicity-full.20170513T103013Z.vol1.difftar.gpg
>>> -> /<path>/temp/duplicity-ZIgjka-tempdir/mktemp-Flkw6b-2
>>>
>>> while:
>>>
>>> ls -ahlrt .temp/duplicity-ZIgjka-tempdir
>>> total 16K
>>> drwx------  2 user user 4.0K May 13 09:49 duplicity_temp.1
>>> drwx------  2 user user 4.0K May 13 09:50 duplicity_temp.2
>>> drwx------  4 user user 4.0K May 13 09:50 .
>>> drwxrwxr-x 11 user user 4.0K May 13 12:01 ..
>>>
>>> And we can see there is no 'mktemp-Flkw6b-2 there.
>>>
>>> There is one file however that's large:
>>>
>>> $ ls -ahlrt /<path>/temp/duplicity-ZI69Av-tempdir/
>>> total 201M
>>> -rw-------  1 user user    0 May 13 12:01 mkstemp-wMMrVz-1
>>> drwxrwxr-x 11 user user 4.0K May 13 12:01 ..
>>> -rw-------  1 user user 201M May 13 12:02 mktemp-sZhQ3Y-2
>>> drwx------  3 user user 4.0K May 13 12:02 .
>>> drwx------  2 user user 4.0K May 13 12:02 duplicity_temp.1
>>>
>>> And ps aux gives us an entry:
>>> 0.0  0.2  73608  2380 pts/5    Ss+  12:02   0:00 /bin/scp
>>> -oServerAliveInterval=15 -oServerAliveCountMax=2 
>>> /home/user/.temp/duplicity-ZI69Av-tempdir/mktemp-sZhQ3Y-2
>>> <user>@<ip>:/<path>/duplicity/duplicity-test+par2/<destination>/
>>> duplicity-full.20170513T120145Z.vol1.difftar.gpg
>>>
>>> You can see the 'transfer' has started at 12:02 and seems to be 
>>> a bit active still (CPU 0.2%). However, at the target the 
>>> destination directory is still completely empty:
>>> $ ls -hl <path>/duplicity/duplicity-test+par2/<destination>
>>> total 0
>>>
>>> What seems to be going on here?
>>>
>>> Harry
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Duplicity-talk mailing list
>>> address@hidden
>>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>