Has anyone figured out the problem yet?

/usr/bin/duplicity -v3 --full-if-older-than 14D --encrypt-key=B8C500C9 --sign-key=B8C500C9 --exclude /share/osowski --exclude /share/michalson --include=/share/kaeding --include=/home/jkaeding --include=/home/malvarado --exclude=** / s3+http://mybucket/marshall

Does that look like it should work? Nothing jumps out at me as being amiss.

One thing you can test is to go to line 210 and add an “echo” before the backup command then see what is being run in your log file.

duplicity_backup()
{
  echo ${DUPLICITY} ${OPTION} ${VERBOSITY} ${STATIC_OPTIONS} \
  --encrypt-key=${GPG_KEY} \
  --sign-key=${GPG_KEY} \
  ${EXCLUDE} \
  ${INCLUDE} \
  ${EXCLUDEROOT} \
  ${ROOT} ${DEST} \
  >> ${LOGFILE}
}

This will output the full command being run rather than execute it — you could see if it looks suspicious …

# ./dt-s3-backup.sh --backup
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1239, in ?
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1232, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1205, in main
    full_backup(col_stats)
  File "/usr/bin/duplicity", line 416, in full_backup
    globals.backend)
  File "/usr/bin/duplicity", line 294, in write_multivol
    globals.gpg_profile, globals.volsize)
  File "/usr/lib/python2.4/site-packages/duplicity/gpg.py", line 272, in GPGWriteFile
    file = GPGFile(True, path.Path(filename), profile)
  File "/usr/lib/python2.4/site-packages/duplicity/gpg.py", line 105, in __init__
    if globals.gpg_options:
AttributeError: 'module' object has no attribute 'gpg_options'

I have set the GPG_KEY variable in your script.

By any chance, would you suggest reverting duplicity back to a version that is known to work with your script? (Of course, if you have any idea how to solve this problem, and use the latest/greatest version, that would be ideal).

Thanks!

Yes, I am using the latest from github, as of earlier today.

PS – are you using the latest code from github ? We have some new features there.

Here is the relevant snippet (I’m pretty sure this is how I downloaded it; I don’t think I modified these lines at all):

# FULL BACKUP & REMOVE OLDER THAN SETTINGS
# Because duplicity will continue to add to each backup as you go,
# it will eventually create a very large set of files.  Also, incremental
# backups leave room for problems in the chain, so doing a "full"
# backup every so often isn't not a bad idea.
#
# You can either remove older than a specific time period:
#CLEAN_UP_TYPE="remove-older-than"
#CLEAN_UP_VARIABLE="31D"

# Or, If you would rather keep a certain (n) number of full backups (rather
# than removing the files based on their age), you can use what I use:
CLEAN_UP_TYPE="remove-all-but-n-full"
CLEAN_UP_VARIABLE="2"

Any ideas?