duplicity-team team mailing list archive

[edso <question209976@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

edso proposed the following answer:
On 30.09.2012 14:11, Michael wrote:
> New question #209976 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/209976
> 
> Hello,
> 
> I am using duplicity 0.6.19 and Python 2.7.3.
> 
> I interrupted a 2 TB initial backup to set a upload speed limit. So I used:
> 
> duplicity --no-encryption --volsize 1000 --asynchronous-upload --ssh-backend pexpect --scp-command "scp -l 10000" /directory ssh://user@server/directory
> 
> The first thing I noticed was, that the speed limit of 10000 KBit/s was not used. 
> 
> Secondly after some hours the backup process crashed with the following output:
> 
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup left a partial set, restarting.
> Last full backup date: Thu Sep 27 13:23:30 2012
> RESTART: Volumes 90 to 90 failed to upload before termination.
>          Restarting backup at volume 90.
> Restarting after volume 89, file path_to_file.jpg, block 0
> File file path_to_file.jpg complete in backup set.
> Continuing restart on file file path_to_file.jpg.
> Traceback (most recent call last):
>   File "/usr/local/bin/duplicity", line 1391, in <module>
>     with_tempdir(main)
>   File "/usr/local/bin/duplicity", line 1384, in with_tempdir
>     fn()
>   File "/usr/local/bin/duplicity", line 1354, in main
>     full_backup(col_stats)
>   File "/usr/local/bin/duplicity", line 500, in full_backup
>     globals.backend)
>   File "/usr/local/bin/duplicity", line 399, in write_multivol
>     (tdp, dest_filename, vol_num)))
>   File "/usr/local/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 151, in schedule_task
>     return self.__run_asynchronously(fn, params)
>   File "/usr/local/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 215, in __run_asynchronously
>     with_lock(self.__cv, wait_for_and_register_launch)
>   File "/usr/local/lib/python2.7/dist-packages/duplicity/dup_threading.py", line 100, in with_lock
>     return fn()
>   File "/usr/local/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 196, in wait_for_and_register_launch
>     check_pending_failure()    # raise on fail
>   File "/usr/local/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 191, in check_pending_failure
>     self.__failed_waiter()
>   File "/usr/local/lib/python2.7/dist-packages/duplicity/dup_threading.py", line 201, in caller
>     value = fn()
>   File "/usr/local/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 183, in <lambda>
>     (waiter, caller) = async_split(lambda: fn(*params))
>   File "/usr/local/bin/duplicity", line 398, in <lambda>
>     async_waiters.append(io_scheduler.schedule_task(lambda tdp, dest_filename, vol_num: put(tdp, dest_filename, vol_num),
>   File "/usr/local/bin/duplicity", line 296, in put
>     backend.put(tdp, dest_filename)
>   File "/usr/local/lib/python2.7/dist-packages/duplicity/backends/_ssh_pexpect.py", line 230, in put
>     self.put_sftp(source_path, remote_filename = remote_filename)
>   File "/usr/local/lib/python2.7/dist-packages/duplicity/backends/_ssh_pexpect.py", line 243, in put_sftp
>     self.run_sftp_command(commandline, commands)
>   File "/usr/local/lib/python2.7/dist-packages/duplicity/backends/_ssh_pexpect.py", line 223, in run_sftp_command
>     log.Warn("Running '%s' with commands:\n %s\n failed (attempt #%d): %s" % (commandline, "\n ".join(commands), n, msg))
> UnboundLocalError: local variable 'msg' referenced before assignment
> 
> Maybe it is worth to do two different bugreports an that topic.
> 

your first issue ain't a bug. see manpage --use-scp explanation
http://duplicity.nongnu.org/duplicity.1.html 

the second should be fixed when
http://bazaar.launchpad.net/~ed.so/duplicity/ssh-pexpect-msgbug/revision/871
will be merged.

..ede/duply.net

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