I recently updated to duplicity 0.7.07 and suddenly my backup to S3 fails. I believe, I managed to trace the issue to duplicity/backends/_boto_single.py. I am running
/usr/bin/duplicity --name duply_system --verbosity 9 / s3://s3-eu-central-1.amazonaws.com/my_bucket/duplicity
with the environment variables
S3_USE_SIGV4=True
AWS_ACCESS_KEY_ID=MYACCESSKEY
AWS_SECRET_ACCESS_KEY=MYSECRET
This fails with the output given below (line number in _boto_single.py approximate as I added some debug output). I managed to reconstruct: In my case, BotoBackend._list fails as self.bucket is None. Before, BotoBackend.resetConnection is called, which sets self.bucket to None. Inside BotoBackend.resetConnection, self.bucket is only set to a valid bucket in case the bucket does not yet exist (in which case it is created via self.conn.create_bucket). In case the bucket already exists, self.bucket is left None. No other attempt inside BotoBackend is made to set self.bucket, eventually letting BotoBackend._list fail.
Output of call:
Using archive dir: /root/.cache/duplicity/duply_system
Using backup name: duply_system
Import of duplicity.backends.acdclibackend Succeeded
Import of duplicity.backends.azurebackend Succeeded
Import of duplicity.backends.b2backend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.copycombackend Succeeded
Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.hubicbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.lftpbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.mediafirebackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.multibackend Succeeded
Import of duplicity.backends.ncftpbackend Succeeded
Import of duplicity.backends.onedrivebackend Succeeded
Import of duplicity.backends.par2backend Succeeded
Import of duplicity.backends.pydrivebackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.ssh_paramiko_backend Succeeded
Import of duplicity.backends.ssh_pexpect_backend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.sxbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Main action: inc
================================================================================
duplicity 0.7.07 ($reldate)
Args: /usr/bin/duplicity --name duply_system --verbosity 9 / s3://s3-eu-central-1.amazonaws.com/backup-git.point-8.de-gitlab/duplicity
Linux git 4.2.0-35-generic #40~14.04.1-Ubuntu SMP Fri Mar 18 16:37:35 UTC 2016 x86_64 x86_64
/usr/bin/python 2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2]
================================================================================
Using temporary directory /tmp/duplicity-OwOHZf-tempdir
Registering (mkstemp) temporary file /tmp/duplicity-OwOHZf-tempdir/mkstemp-gDTnhP-1
Temp has 35986862080 available, backup will use approx 34078720.
Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 367, in inner_retry
return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 569, in list
return [tobytes(x) for x in self.backend._list()]
File "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", line 253, in _list
raise BackendException("No connection to backend")
BackendException: No connection to backend
Attempt 1 failed. BackendException: No connection to backend
Modifying resetConnection to
def resetConnection
import boto
if getattr(self, 'conn', False):
self.bucket = None
self.conn = None
del self.conn
del self.storage_uri
self.conn = get_connection(
if not self.conn.
if globals.
else:
else:
seems to resolve the issue. Although, I am not sure if this is wise (found this while trial-and-erroring through the file).