[Duplicity-talk] Crash with duplicity 0.7.06

[Scott Hannahs]

The following command gives the included traceback, is this a known issue? Not sure what the issue is, since I have it working on 3 other directories with the same command. The command is in a loop in a script that just uses different directories. I am not clear what this error means, it seems to say that remote target is not reachable. But this subsequently works with the same host for 3 other directories. That folder in the bucket does exist but is empty.

Any thoughts?
-Scott

nice -n19 /sw/bin/duplicity --full-if-older-than 32D --num-retries 5 --tempdir /var/tmp/duplicity --volsize 250 --asynchronous-upload --encrypt-key XXXXXXXX --sign-key YYYYYYYY --gpg-options=--default-key=YYYYYYYY --force --verbosity Notice --s3-unencrypted-connection --s3-use-new-style --allow-source-mismatch --exclude **/Documents/Virtual?Machines.localized --exclude **/Library/Caches --exclude **/Library/Mail --exclude **/Library/Mail?Downloads --exclude **/Library/Application?Support/Google --exclude **/Library/Application?Support/Microsoft --exclude **/Library/Application?Support/WebEx?Folder /Users/WWW/Documents s3://objects.dreamhost.com//ZZZZZZZ-20150813-backups/documents

Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
Last full backup is too old, forcing full backup
Attempt 1 failed. gaierror: [Errno 8] nodename nor servname provided, or not known

============================= ERROR LOG ===========================

Traceback (most recent call last):
File "/sw/bin/duplicity", line 1532, in <module>
with_tempdir(main)
File "/sw/bin/duplicity", line 1526, in with_tempdir
fn()
File "/sw/bin/duplicity", line 1380, in main
do_backup(action)
File "/sw/bin/duplicity", line 1496, in do_backup
full_backup(col_stats)
File "/sw/bin/duplicity", line 567, in full_backup
globals.backend)
File "/sw/bin/duplicity", line 448, in write_multivol
(tdp, dest_filename, vol_num)))
File "/sw/lib/python2.7/site-packages/duplicity/asyncscheduler.py", line 152, in schedule_task
return self.__run_asynchronously(fn, params)
File "/sw/lib/python2.7/site-packages/duplicity/asyncscheduler.py", line 216, in __run_asynchronously
with_lock(self.__cv, wait_for_and_register_launch)
File "/sw/lib/python2.7/site-packages/duplicity/dup_threading.py", line 105, in with_lock
return fn()
File "/sw/lib/python2.7/site-packages/duplicity/asyncscheduler.py", line 197, in wait_for_and_register_launch
check_pending_failure() # raise on fail
File "/sw/lib/python2.7/site-packages/duplicity/asyncscheduler.py", line 192, in check_pending_failure
self.__failed_waiter()
File "/sw/lib/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’



The “status” command on that directory shows that it is empty but runs correctly.

### Status ### Documents Sun Mar 20 04:06:57 EDT 2016
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
Collection Status
-----------------
Connecting with backend: BackendWrapper
Archive dir: /Users/WWW/.cache/duplicity/0f2dc92338d11c748b7fe2ee5c420f28

Found 0 secondary backup chains.
No backup chains with active signatures found
No orphaned or incomplete backup sets found.