Re: [Duplicity-talk] gpg: invalid packet

[Kenneth Loafman]

Paul wrote:
> I've been running nightly backups to Amazon S3 with Duplicity 0.5.18 and
> GnuPG 1.4.6 on Debian etch for several months. Just recently I started
> seeing errors like the following. Any suggestions for how to debug this?
> 
> Thanks!
> 
> 
> 
> python: ERROR: (rs_loadsig_s_stronglen) strong sum length 112 is
> implausible
> python: ERROR: (rs_job_complete) loadsig job failed: stream corrupt
> Error librsync error 106 while in delta rs_signature_t builder getting
> delta for
> home/heidi/Maildir/.savedmessages.saved-messages-060103060630/cur/1206141498.000365.mbox:2,S
> 
> tarfile: Bad Checksum
> python: ERROR: (rs_loadsig_s_stronglen) strong sum length 54 is implausible
> python: ERROR: (rs_job_complete) loadsig job failed: stream corrupt
> Error librsync error 106 while in delta rs_signature_t builder getting
> delta for
> home/heidi/Maildir/.savedmessages.saved-messages-060103060630/cur/1206141498.000375.mbox:2,S
> 
> tarfile: Bad Checksum
> Error librsync error 1 while in delta rs_signature_t builder getting
> delta for
> home/heidi/Maildir/.savedmessages.saved-messages-060103060630/cur/1206141498.000385.mbox:2,S
> 
> tarfile: Bad Checksum
> python: ERROR: (rs_loadsig_s_stronglen) strong sum length 144 is
> implausible
> python: ERROR: (rs_job_complete) loadsig job failed: stream corrupt
> Error librsync error 106 while in delta rs_signature_t builder getting
> delta for
> home/heidi/Maildir/.savedmessages.saved-messages-060103060630/cur/1206141498.000395.mbox:2,S

Given the Bad Checksum error on the tarfile, my guess would be that one
of the last few backup files is corrupted, probably a sigtar file given
that librsync is involved.

Try doing a full backup and the problem will go away on its own.

Or, if you want to keep doing more incrementals, try going back to the
date this started and removing all the incrementals beginning one day
before that.  Or, just move them out of the way till you test it.

Or, if you're really masochistic, decrypt all the files, and run
    $ for f in *sigtar*; do tar t $f; done
and that should give you an error on the one that's gone bad.  Then just
remove that one and all the incrementals after that.  Don't forget to
re-encrypt the files before firing off duplicity.

The first option is the best.

...Ken

signature.asc
Description: OpenPGP digital signature