Hmmm.. For some reason my
cache doesn't have files ending with difftar.gpg:
# ls *
Turning the cache folder over (and it is not running out of space, there
is tons available), I'm still getting the same error. I'll post stuff
to Pastebin shortly for you guys to see more of the output.
looks like the
error is happening when trying to read an
existing signature tarfile,
which is something duplicity uses
internally to determine which
files have changed and such.
have lots of those files. It would help to see which one is
you pain. You'll have two copies of each, one in your cache
in Amazon S3. For now, let's look at the ones in the cache.
Brief aside, if you move ~/.cache/duplicity aside (*Do not delete,
move it back after testing this*), do you get the same behavior
you try your backup command?
So let's try to find which of your
existing cache sigtar files might be bogus:
~/.cache/duplicity/* (whichever cache directory is being used here)
--multifile --decrypt duplicity*signatures.*.*.difftar.gpg
for t in
duplicity-full.20110127T131352Z.*.difftar; do tar xf $t; done
is rather a shotgun approach, that will decrypt and untar all
signature files. You can delete them safely afterward, I'm just
to see which, if any, tar will complain about.
yes.. i need to see
what is going on: espeially command line and maybe 100 lines before the
stack.. something like that. you can as well just attach a compressed
file if pastebin says it's to big.
It's an absolutely massive
backup, do you mean this literally? Everything before the snipped stuff
was just pages upon pages of file comparison output. There was nothing
unusual immediately before the Pastebin output other than another file