Bug 1331979 - deja-dup S3 backend "Giving up after 5 attempts. BackendException: No connection to backend"
Summary: deja-dup S3 backend "Giving up after 5 attempts. BackendException: No connect...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: duplicity
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-30 21:58 UTC by Jorge Martínez López
Modified: 2016-06-08 14:43 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-08 14:43:40 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jorge Martínez López 2016-04-30 21:58:42 UTC 
Description of problem:
Backup to Amazon S3 fails after 5 attempts.


Version-Release number of selected component (if applicable):
deja-dup-34.2-1.fc23.x86_64

How reproducible:
deja-dup --backup


Steps to Reproduce:
1.
2.
3.

Actual results:
"Giving up after 5 attempts. BackendException: No connection to backend"

Expected results:


Additional info:

DUPLICITY: DEBUG 1
DUPLICITY: . Backtrace of previous error: Traceback (innermost last):
DUPLICITY: .   File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 367, in inner_retry
DUPLICITY: .     return fn(self, *args)
DUPLICITY: .   File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 569, in list
DUPLICITY: .     return [tobytes(x) for x in self.backend._list()]
DUPLICITY: .   File "/usr/lib64/python2.7/site-packages/duplicity/backends/_boto_single.py", line 252, in _list
DUPLICITY: .     raise BackendException("No connection to backend")
DUPLICITY: .  BackendException: No connection to backend
DUPLICITY: . 

DUPLICITY: ERROR 50 list
DUPLICITY: . Giving up after 5 attempts. BackendException: No connection to backend


Perhaps related to https://bugs.launchpad.net/deja-dup/+bug/1572096 ?
Comment 1 Jorge Martínez López 2016-04-30 22:04:22 UTC 
Just tried downgrading duplicity from duplicity-0.7.07-1.fc23.x86_64 to duplicity-0.7.05-1.fc23.x86_64 and now it works.
Comment 2 Major Hayden 🤠 2016-05-04 14:24:34 UTC 
I have the same issue with the Google Storage backend (uses boto, like the S3 backend does).  Downgrading duplicity works fine.  Also, installing duplicity-0.7.7.1 from the upstream source works fine, too.

The issue seems to be in duplicity since changing boto versions has no effect.
Comment 3 Gwyn Ciesla 2016-05-04 15:26:46 UTC 
Does that include boto 2.40.0?
Comment 4 Craig Robson 2016-05-09 02:58:49 UTC 
I see that my last good backup was the day before the duplicity update too.
Comment 5 Jorge Martínez López 2016-06-04 12:23:12 UTC 
Upgraded to duplicity-0.7.07.1-1.fc23.x86_64 and it works fine now so I guess this bug can be closed.
Comment 6 Gwyn Ciesla 2016-06-08 14:43:40 UTC 
Excellent!
Note You need to log in before you can comment on or make changes to this bug.