connection reset on backup to s3 target
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Déjà Dup |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Release: Ubuntu 14.04.2 LTS
Packages: deja-dup 30.0-0ubuntu4, duplicity 0.6.23-1ubuntu4.1
Gnome Conf Settings:
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic false
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 's3'
org.gnome.DejaDup last-run '2015-03-
org.gnome.DejaDup nag-check '2015-03-
org.gnome.DejaDup prompt-check 'disabled'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup last-backup '2015-03-
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup delete-after 0
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
Backing up to s3 fails due to problems with python boto / duplicity which were fixed upstream but apparently have not made it to LTS. Backup to s3 fails due to connection reset error 104. I believe this is due to new signature requirements which were added to s3 requests approximately 1 year ago. A snippet of the error message from duplicity is as follows:
DUPLICITY: INFO 1
DUPLICITY: . Uploading s3+http://
DUPLICITY: WARNING 1
DUPLICITY: . Upload 's3+http://
DUPLICITY: DEBUG 1
DUPLICITY: . Backtrace of previous error: Traceback (innermost last):
DUPLICITY: . File "/usr/lib/
DUPLICITY: . num_cb=(max(2, 8 * globals.volsize / (1024 * 1024)))
DUPLICITY: . File "/usr/lib/
DUPLICITY: . encrypt_
DUPLICITY: . File "/usr/lib/
DUPLICITY: . chunked_
DUPLICITY: . File "/usr/lib/
DUPLICITY: . chunked_
DUPLICITY: . File "/usr/lib/
DUPLICITY: . query_args=
DUPLICITY: . File "/usr/lib/
DUPLICITY: . retry_handler=
DUPLICITY: . File "/usr/lib/
DUPLICITY: . retry_handler=
DUPLICITY: . File "/usr/lib/
DUPLICITY: . request.body, request.headers)
DUPLICITY: . File "/usr/lib/
DUPLICITY: . http_conn.
DUPLICITY: . File "/usr/lib/
DUPLICITY: . self.sock.
DUPLICITY: . File "/usr/lib/
DUPLICITY: . v = self.send(
DUPLICITY: . File "/usr/lib/
DUPLICITY: . v = self._sslobj.
DUPLICITY: . error: [Errno 104] Connection reset by peer
DUPLICITY: .
DUPLICITY: WARNING 1
DUPLICITY: . Giving up trying to upload s3+http://
DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile <lockfile.
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-
DUPLICITY: INFO 1
DUPLICITY: . Backend error detail: Traceback (most recent call last):
DUPLICITY: . File "/usr/bin/
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File "/usr/bin/
DUPLICITY: . fn()
DUPLICITY: . File "/usr/bin/
DUPLICITY: . do_backup(action)
DUPLICITY: . File "/usr/bin/
DUPLICITY: . full_backup(
DUPLICITY: . File "/usr/bin/
DUPLICITY: . globals.backend)
DUPLICITY: . File "/usr/bin/
DUPLICITY: . (tdp, dest_filename, vol_num)))
DUPLICITY: . File "/usr/lib/
DUPLICITY: . return self.__
DUPLICITY: . File "/usr/lib/
DUPLICITY: . ret = fn(*params)
DUPLICITY: . File "/usr/bin/
DUPLICITY: . async_waiters.
DUPLICITY: . File "/usr/bin/
DUPLICITY: . backend.put(tdp, dest_filename)
DUPLICITY: . File "/usr/lib/
DUPLICITY: . raise BackendExceptio
DUPLICITY: . BackendException: Error uploading s3+http://
DUPLICITY: .
DUPLICITY: ERROR 23 BackendException
DUPLICITY: . BackendException: Error uploading s3+http://
This is a widely reported issue with older versions of boto+duplicity.
I have the same issue. S3 backup is broken.
deja-dup 34.0-1ubuntu3
Ubuntu Gnome 15.10
python-cloudfiles 1.7.11-3
python-boto 2.38.0-1ubuntu1
duplicity 0.7.02-1ubuntu1