duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Duplicity-talk] Completely broken the backup process when upgraded to 0


From: howard chen
Subject: [Duplicity-talk] Completely broken the backup process when upgraded to 0.6.20 ([Errno 104] Connection reset by peer)
Date: Thu, 15 Nov 2012 15:32:34 +0800

We are using 0.6.1 and updated to 0.6.20 and the backup process failed completely, 

with the error (without -v)

Local and Remote metadata are synchronized, no sync needed.
Last full backup left a partial set, restarting.
Last full backup date: Thu Nov 15 07:10:08 2012
RESTART: The first volume failed to upload before termination.
         Restart is impossible...starting backup from beginning.
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
Last full backup is too old, forcing full backup
Upload 's3+http://duplicity-example-0.6.20/duplicity-full.20121115T072103Z.vol1.difftar.gpg' failed (attempt #1, reason: error: [Errno 104] Connection reset by peer)
Upload 's3+http://duplicity-example-0.6.20/duplicity-full.20121115T072103Z.vol1.difftar.gpg' failed (attempt #2, reason: error: [Errno 32] Broken pipe)
Upload 's3+http://duplicity-example-0.6.20/duplicity-full.20121115T072103Z.vol1.difftar.gpg' failed (attempt #3, reason: error: [Errno 32] Broken pipe)
Upload 's3+http://duplicity-example-0.6.20/duplicity-full.20121115T072103Z.vol1.difftar.gpg' failed (attempt #4, reason: error: [Errno 104] Connection reset by peer)


with -v9

Uploading s3+http://duplicity-example-0.6.20/duplicity-full.20121115T072849Z.vol1.difftar.gpg to STANDARD Storage
Upload 's3+http://duplicity-example-0.6.20/duplicity-full.20121115T072849Z.vol1.difftar.gpg' failed (attempt #1, reason: error: [Errno 104] Connection reset by peer)
Backtrace of previous error: Traceback (innermost last):
  File "/usr/lib/python2.6/dist-packages/duplicity/backends/_boto_single.py", line 215, in put
    'x-amz-storage-class': storage_class})
  File "/usr/lib/pymodules/python2.6/boto/s3/key.py", line 498, in set_contents_from_filename
    self.set_contents_from_file(fp, headers, replace, cb, num_cb, policy)
  File "/usr/lib/pymodules/python2.6/boto/s3/key.py", line 455, in set_contents_from_file
    self.send_file(fp, headers, cb, num_cb)
  File "/usr/lib/pymodules/python2.6/boto/s3/key.py", line 367, in send_file
    self.name, headers, sender=sender)
  File "/usr/lib/pymodules/python2.6/boto/s3/connection.py", line 342, in make_request
    data, host, auth_path, sender)
  File "/usr/lib/pymodules/python2.6/boto/connection.py", line 459, in make_request
    return self._mexe(method, path, data, headers, host, sender)
  File "/usr/lib/pymodules/python2.6/boto/connection.py", line 437, in _mexe
    raise e
 error: [Errno 104] Connection reset by peer




The backup is definitely okay before the upgrade. 
Any idea?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]