[Duplicity-talk] linux backup stopped unexpectedly

[c***@ccs.covici.com]

I have been doing a linux backup to azure storage for several days and
it has stopped unexpectedly with the following traceback

AsyncScheduler: a previously scheduled task has failed; propagating the
result immediately
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1537, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1531, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1385, in main
do_backup(action)
File "/usr/bin/duplicity", line 1501, in do_backup
full_backup(col_stats)
File "/usr/bin/duplicity", line 572, in
full_backup
globals.backend)
File "/usr/bin/duplicity", line 453, in
write_multivol
(tdp, dest_filename, vol_num)))
File
"/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py",
line 152, in schedule_task
return
self.__run_asynchronously(fn,
params)
File
"/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py",
line 216, in
__run_asynchronously
with_lock(self.__cv,
wait_for_and_register_launch)
File
"/usr/lib64/python2.7/site-packages/duplicity/dup_threading.py",
line 105, in with_lock
return fn()
File
"/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py",
line 208, in
wait_for_and_register_launch
check_pending_failure()
# raise on
fail
File
"/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py",
line 192,
in
check_pending_failure
self.__failed_waiter()
File
"/usr/lib64/python2.7/site-packages/duplicity/dup_threading.py",
line
201,
in
waiter
raise
state['error'].with_traceback(state['trace'])
AttributeError:
'exceptions.AttributeError'
object
has
no
attribute
'with_traceback'

Is --async-upload not a good idea?


Any suggestions would be greatly appreciated.