Amazon S3 backup: Giving up after 5 attempts. BackendException: No connection to backend

Bug #1572096 reported by Sander
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Déjà Dup
Invalid
Undecided
Unassigned

Bug Description

I seem to have a problem with the DejaDup backing up to my Amazon S3 storage. Everything was working before, but now it stopped working. I didn't change any settings in the meantime, but there has been an update of DejaDup from version 34.1-2 to 34.2-1 (I'm running Arch), after which this problem started occuring. The duplicity version on my system is 0.7.07-1.

This is the error I get from DejaDup:
Giving up after 5 attempts. BackendException: No connection to backend

I generated a log file, this might be more useful. I attached it to this bug report. Also I attached my DejaDup settings.

Thanks!

Revision history for this message
Sander (sanderth-deactivatedaccount) wrote :
Revision history for this message
Sander (sanderth-deactivatedaccount) wrote :
Revision history for this message
Remis (plremis) wrote :

I have the same issue after 34.2 upgrade.

I've checked in another workstation with the deja-dup 34.1 , same settings, same target storage, similar environment (Vanilla Gnome 3, Fedora 23 WorkStation), and everything is working fine.

On my workstation I get the same message:

`Giving up after 5 attempts. BackendException: No connection to backend`

When I try `deja-dup --backup` from the command line, on my workstation, I get this:

---

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 1369, in main
    action = commandline.ProcessCommandLine(sys.argv[1:])
  File "/usr/lib64/python2.7/site-packages/duplicity/commandline.py", line 1109, in ProcessCommandLine
    globals.backend = backend.get_backend(args[0])
  File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 223, in get_backend
    obj = get_backend_object(url_string)
  File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 209, in get_backend_object
    return factory(pu)
  File "/usr/lib64/python2.7/site-packages/duplicity/backends/_boto_single.py", line 161, in __init__
    self.resetConnection()
  File "/usr/lib64/python2.7/site-packages/duplicity/backends/_boto_single.py", line 183, in resetConnection
    self.conn = get_connection(self.scheme, self.parsed_url, self.storage_uri)
  File "/usr/lib64/python2.7/site-packages/duplicity/backends/_boto_single.py", line 95, in get_connection
    conn = storage_uri.connect(is_secure=(not globals.s3_unencrypted_connection))
  File "/usr/lib/python2.7/site-packages/boto-2.39.0-py2.7.egg/boto/storage_uri.py", line 117, in connect
    **connection_args)
  File "/usr/lib/python2.7/site-packages/boto-2.39.0-py2.7.egg/boto/s3/connection.py", line 197, in __init__
    "When using SigV4, you must specify a 'host' parameter."
HostRequiredError: BotoClientError: When using SigV4, you must specify a 'host' parameter.

---

Revision history for this message
Moreno (ymoreno) wrote :

Confirmed

Revision history for this message
Michael Terry (mterry) wrote :

This is not a bug in deja-dup, but seemingly python-boto (or maybe duplicity?). Does it work now with latest versions of those?

Changed in deja-dup:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.