Resuming a failed backup with Assertion errors
My first incremental backup failed roughly 60GB into the upload. This was due to my router dying on me, thus no internet connection. Here is the log of that backup, including all (including the final) connection failure errors:
root@myserver:~$ sudo /usr/local/
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Thu Dec 16 19:37:21 2010
exit^[Upload 's3+http://
Upload 's3+http://
Upload 's3+http://
Upload 's3+http://
sudUpload 's3+http://
sUpload 's3+http://
Upload 's3+http://
Upload 's3+http://
Upload 's3+http://
ame resolution)
Upload 's3+http://
ame resolution)
Giving up trying to upload s3+http://
BackendException: Error uploading s3+http://
Now, when I try to resume the upload, I get:
root@myserver:~$ /usr/local/
Local and Remote metadata are synchronized, no sync needed.
Traceback (most recent call last):
File "/usr/bin/
with_
File "/usr/bin/
fn()
File "/usr/bin/
globals.
File "/usr/lib/
self.
File "/usr/lib/
map(
File "/usr/lib/
if set.add_
File "/usr/lib/
self.
File "/usr/lib/
remote_
AssertionError: ('duplicity-
Is there any way to fix this and resume the backup?
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Duplicity Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Move the local cache from ~/.cache/duplicity to ~/.cache/
restart the incremental.
If that works, remove ~/.cache/
again.
If that does not work, use -v9 in the duplicity command and save the log.
Please post the first 200 lines and the last 200 lines of the run. Munge
any personal information, but be very careful not to modify the format of
the logging.
...Ken
On Wed, Jan 12, 2011 at 9:30 AM, vergueishon <
<email address hidden>> wrote:
> Question #141176 on Duplicity changed:
> https:/
>
> Description changed to:
> My first incremental backup failed roughly 60GB into the upload. This
> was due to my router dying on me, thus no internet connection. Here is
> the log of that backup, including all (including the final) connection
> failure errors:
>
> root@myserver:~$ sudo /usr/local/
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Thu Dec 16 19:37:21 2010
> exit^[Upload 's3+
> http://
> failed (attempt #1, reason: error: [Errno 32] Broken pipe)
> Upload 's3+
> http://
> failed (attempt #1, reason: error: [Errno 32] Broken pipe)
> Upload 's3+
> http://
> failed (attempt #1, reason: error: [Errno 32] Broken pipe)
> Upload 's3+
> http://
> failed (attempt #2, reason: error: [Errno 32] Broken pipe)
> sudUpload 's3+
> http://
> failed (attempt #1, reason: gaierror: [Errno -3] Temporary failure in name
> resolution)
> sUpload 's3+
> http://
> failed (attempt #1, reason: gaierror: [Errno -3] Temporary failure in name
> resolution)
> Upload 's3+
> http://
> failed (attempt #2, reason: gaierror: [Errno -3] Temporary failure in name
> resolution)
> Upload 's3+
> http://
> failed (attempt #3, reason: gaierror: [Errno -3] Temporary failure in name
> resolution)
> Upload 's3+
> http://
> failed (attempt #4, reason: gaierror: [Errno -3] Temporary failure in n
> ame resolution)
> Upload 's3+
> http://
> failed (attempt #5, reason: gaierror: [Errno -3] Temporary failure in n
> ame resolution)
> Giving up trying to upload s3+
> http://
> BackendException: Error uploading s3+
> http://
>
> Now, when I try to resume the upload, I get:
>
> root@myserver:~$ /usr/local/
> Local and Remote metadata are synchronized, no sync needed.
> Traceback (most recent call last):
> File "/usr/bin/
> with_tempdir(main)
> File "/usr/bin/
> fn()
> File "/usr/bin/
> globals.
> File "/usr/lib/
> 681, in set_values
> self.get_
> File "/usr/lib/
> 804, in get_backup_chains
> map(add_to_sets, filename_list)
> File "/usr/lib/
> 794, in add_to_sets
> if set.add_
> File "/usr/lib/
> in add_filename
> self.set_
> File "/usr/lib/
> 118, in set_manifest
> remote_filename)
> AssertionError: ('duplicity-
> 'duplicity-
>
> Is there any way to fix this and resume the backup?
>
> --
> You received this question notification because you are a member of
> duplicity-team, which is an answer contact for Duplicity.
>
> _______
> Mailing list: https:/
> Post to : <email address hidden>
> Unsubscribe : https:/
> More help : https:/
>
Revision history for this message
|
#2 |
Tried moving the cache, same error:
root@myserver:~$ /usr/local/
Synchronizing remote metadata to local cache...
Copying duplicity-
Copying duplicity-
Traceback (most recent call last):
File "/usr/bin/
with_
File "/usr/bin/
fn()
File "/usr/bin/
globals.
File "/usr/lib/
self.
File "/usr/lib/
map(
File "/usr/lib/
if set.add_
File "/usr/lib/
self.
File "/usr/lib/
remote_
AssertionError: ('duplicity-
So, here is the first and last 200 lines output with -v9:
Using archive dir: /home/me/
Using backup name: 1341cba2b333f71
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Main action: inc
=======
duplicity 0.6.08b (March 11, 2010)
Args: /usr/bin/duplicity -v9 --encrypt-
Linux myserver 2.6.32-24-server #43-Ubuntu SMP Thu Sep 16 16:05:42 UTC 2010 x86_64
/usr/bin/python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
[GCC 4.4.3]
=======
Using temporary directory /tmp/duplicity-
Registering (mkstemp) temporary file /tmp/duplicity-
Temp has 48061829120 available, backup will use approx 34078720.
Listing s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
Listed s3+http://
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
File duplicity-
Ignoring file (rejected by backup set) 'duplicity-
Removing still remembered temporary file /tmp/duplicity-
Thanks again for your help!
Revision history for this message
|
#4 |
On 26.01.2011 16:35, vergueishon wrote:
> Question #141176 on Duplicity changed:
> https:/
>
> vergueishon posted a new comment:
> bump ... anyone?
>
Best bet for now would be to start a new chain. Resuming interrupted backups is still a very new feature and the assertion coming up looks unpromising to resume to me.
@ken: could you please have a look at the error stack from above and
http://
and shed some light on what this assertion is for? I see it get's a filename. Shouldn't that suffice?
ede/duply.net
Revision history for this message
|
#5 |
Thanks, edso. I suspected that might be the best way to go. Sigh.
Not sure whether to mark your reply as a solution?
Revision history for this message
|
#6 |
On 26.01.2011 20:01, vergueishon wrote:
> Question #141176 on Duplicity changed:
> https:/
>
> vergueishon posted a new comment:
> Thanks, edso. I suspected that might be the best way to go. Sigh.
>
> Not sure whether to mark your reply as a solution?
>
if you've got the time wait for an answer by the maintainer ken, the ticket will close itself eventually and no you didn't get a solution. hence no need to close the ticket.
if not, please backup to another folder or download the erronous backup to somewhere local and create a bug ticket. we perhaps need the backup later to pin down the issue together with you.
..ede/duply.net
Revision history for this message
|
#7 |
Wed, Jan 26, 2011 at 1:12 PM, edso <email address hidden>wrote:
> Question #141176 on Duplicity changed:
> https:/
>
> edso proposed the following answer:
> On 26.01.2011 20:01, vergueishon wrote:
> > Question #141176 on Duplicity changed:
> > https:/
> >
> > vergueishon posted a new comment:
> > Thanks, edso. I suspected that might be the best way to go. Sigh.
> >
> > Not sure whether to mark your reply as a solution?
> >
>
> if you've got the time wait for an answer by the maintainer ken, the
> ticket will close itself eventually and no you didn't get a solution.
> hence no need to close the ticket.
>
> if not, please backup to another folder or download the erronous backup
> to somewhere local and create a bug ticket. we perhaps need the backup
> later to pin down the issue together with you.
>
There have been a lot of fixes since 0.6.08b. I would suggest upgrading to
0.6.11 and trying that out before giving up.
https:/
...Thanks,
...Ken
Revision history for this message
|
#8 |
Thanks for your help, guys. I re-attempted with 0.6.11, but same thing. I've cleared my cache and started a full backup.
I'll do my best to keep the data around for your reference, but no promises!
Revision history for this message
|
#9 |
I've installed 0.6.11 on debian lenny and, when I try to backup to S3, I got this:
Upload 's3+http://
Backtrace of previous error: Traceback (innermost last):
File "/usr/local/
'x-
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.name, headers, sender=sender)
File "/usr/lib/
data, host, auth_path, sender)
File "/usr/lib/
return self._mexe(method, path, data, headers, host, sender)
File "/usr/lib/
raise e
error: (32, 'Broken pipe')
I've installed python-
I use this command:
duplicity -v9 --encrypt-key=xxx --sign-key=xxx --s3-use-new-style --s3-european-
--volsize 250 --name test_www /var/www s3+http://
Can you help me?
Revision history for this message
|
#10 |
After 10 minutes, now seems that upload to S3 works ok...
Revision history for this message
|
#11 |
Hello,
@vergueishon:
This bug has been reported here:
https:/
but there's no follow up as for now
F
Can you help with this problem?
Provide an answer of your own, or ask vergueishon for more information if necessary.