Description of problem: When using Duplicity I receive the error "BackendException: No connection to backend" when attempting to backup to Amazon S3. Version-Release number of selected component (if applicable): 0.6.24-2.fc20 How reproducible: Always Steps to Reproduce: 1. Attempt to backup using Deja-Dup to Amazon S3 2. 3. Actual results: BackendException: No connection to backend Expected results: Backup occurs. Additional info:
On F19 I experienced the same behavior. I haven't tested exhaustively, but I believe I have it working by *both*: 1) creating ~/.boto per http://boto.readthedocs.org/en/latest/getting_started.html 2) manually creating the buckets I wanted to use for the backups
Experiencing the same issue here F19 x64 deja-dup-26.0-1.fc19.x86_64 Dave Allan's workaround is functional; to findout the correct bucket it's trying to use however run: DEJA_DUP_DEBUG=1 deja-dup --backup Pay attention to the DUPLICITY: . Args: /usr/bin/duplicity collection-status line, --s3-use-new-style s3+http://deja-dup-auto-XXXXXXXXXXXX/YOUR_FOLDER DUPLICITY: INFO 1 DUPLICITY: . Backend error detail: Traceback (most recent call last): DUPLICITY: . File "/usr/bin/duplicity", line 1502, in <module> DUPLICITY: . with_tempdir(main) DUPLICITY: . File "/usr/bin/duplicity", line 1496, in with_tempdir DUPLICITY: . fn() DUPLICITY: . File "/usr/bin/duplicity", line 1345, in main DUPLICITY: . do_backup(action) DUPLICITY: . File "/usr/bin/duplicity", line 1374, in do_backup DUPLICITY: . sync_archive(decrypt) DUPLICITY: . File "/usr/bin/duplicity", line 1104, in sync_archive DUPLICITY: . remlist = globals.backend.list() DUPLICITY: . File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 429, in list DUPLICITY: . return map(tobytes, self._list()) DUPLICITY: . File "/usr/lib64/python2.7/site-packages/duplicity/backends/_boto_single.py", line 297, in _list DUPLICITY: . raise BackendException("No connection to backend") DUPLICITY: . BackendException: No connection to backend DUPLICITY: . DUPLICITY: ERROR 23 BackendException DUPLICITY: . BackendException: No connection to backend 1) The error is miss leading the connection to s3 appears fine; this is instead the absense of a bucket being present (additional checking required). 2) deja _used_ to auto create buckets; but no longer does so (regression?) 3) From the gui you may specify the folder but not the bucket compounding the issue.
ok spoke too soon now seeing: DUPLICITY: WARNING 1 DUPLICITY: . Upload 's3+http://deja-dup-auto-XXXXXXXXXX/YYYYYYYYYY/duplicity-full.20140704T155414Z.vol1.difftar.gpg' failed (attempt #2, reason: error: [Errno 104] Connection reset by peer) DUPLICITY: DEBUG 1 DUPLICITY: . Backtrace of previous error: Traceback (innermost last): DUPLICITY: . File "/usr/lib64/python2.7/site-packages/duplicity/backends/_boto_single.py", line 248, in put DUPLICITY: . self.upload(source_path.name, key, headers) DUPLICITY: . File "/usr/lib64/python2.7/site-packages/duplicity/backends/_boto_single.py", line 365, in upload DUPLICITY: . num_cb=(max(2, 8 * globals.volsize / (1024 * 1024))) DUPLICITY: . File "/usr/lib/python2.7/site-packages/boto/s3/key.py", line 1315, in set_contents_from_filename DUPLICITY: . encrypt_key=encrypt_key) DUPLICITY: . File "/usr/lib/python2.7/site-packages/boto/s3/key.py", line 1246, in set_contents_from_file DUPLICITY: . chunked_transfer=chunked_transfer, size=size) DUPLICITY: . File "/usr/lib/python2.7/site-packages/boto/s3/key.py", line 725, in send_file DUPLICITY: . chunked_transfer=chunked_transfer, size=size) DUPLICITY: . File "/usr/lib/python2.7/site-packages/boto/s3/key.py", line 914, in _send_file_internal DUPLICITY: . query_args=query_args DUPLICITY: . File "/usr/lib/python2.7/site-packages/boto/s3/connection.py", line 633, in make_request DUPLICITY: . retry_handler=retry_handler DUPLICITY: . File "/usr/lib/python2.7/site-packages/boto/connection.py", line 1046, in make_request DUPLICITY: . retry_handler=retry_handler) DUPLICITY: . File "/usr/lib/python2.7/site-packages/boto/connection.py", line 919, in _mexe DUPLICITY: . request.body, request.headers) DUPLICITY: . File "/usr/lib/python2.7/site-packages/boto/s3/key.py", line 815, in sender DUPLICITY: . http_conn.send(chunk) DUPLICITY: . File "/usr/lib64/python2.7/httplib.py", line 805, in send DUPLICITY: . self.sock.sendall(data) DUPLICITY: . File "/usr/lib64/python2.7/ssl.py", line 229, in sendall DUPLICITY: . v = self.send(data[count:]) DUPLICITY: . File "/usr/lib64/python2.7/ssl.py", line 198, in send DUPLICITY: . v = self._sslobj.write(data) DUPLICITY: . error: [Errno 104] Connection reset by peer DUPLICITY: . due to the url s3+http whilst attempting SSL write?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
According to the Launchpad bug this is fixed in 0.7.01, which is in rawhide but not F21 or F22. A backport or version update would be dandy.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.