Re: [Duplicity-talk] duplicity backup failed to restart after failure

[John Covici]

Well, I did the clean, but there was nothing there, and there was no
*.part files, so I ran the incremental again and it worked.  I hope
there are no orphaned files in the back end.

Thanks for all your help.

As to the internet outage, I probably deleted the lock file when I
killed the job.  The errors are in the log, but for some reason it
kept going.

On Sun, 06 Nov 2016 08:00:23 -0500,
address@hidden wrote:
> 
> ok, your log of the "actual failure job" did not contain any error. but if it 
> really was still lingering in memory than there should have been a lockfile 
> prohibiting your attempt to run the backup again until you finished the still 
> running job.
> 
> wrt. your original question. running 'duplicity clean' should offer you to 
> delete the unfinished backup (use --force to actually delete) so the next run 
> will not try to resume it. if that does not work you can manually delete all 
> files of the offending backup 
> 'duplicity-inc.20161103T070100Z.to.20161104T070101Z.*' from the backend.
> 
> ..ede/duply.net
> 
> On 05.11.2016 11:27, John Covici via Duplicity-talk wrote:
> > Also, I discovered that the actual failure job never correctly
> > terminated for more than 24 hours as well.  It just hung there.
> > 
> > On Sat, 05 Nov 2016 06:19:56 -0400,
> > John Covici via Duplicity-talk wrote:
> >>
> >> Hi.  Due to losing the internet, my last incremental backup did not
> >> work -- that  I can understand, but when I tried to run the
> >> incremental backup again, it would not restart.  Here is the log I got
> >> trying to restart
> >> Using archive dir: /root/.cache/duplicity/backup_linux
> >> Using backup name: backup_linux
> >> Import of duplicity.backends.acdclibackend Succeeded
> >> Import of duplicity.backends.azurebackend Succeeded
> >> Import of duplicity.backends.b2backend Succeeded
> >> Import of duplicity.backends.botobackend Succeeded
> >> Import of duplicity.backends.cfbackend Succeeded
> >> Import of duplicity.backends.copycombackend Succeeded
> >> Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
> >> Import of duplicity.backends.gdocsbackend Succeeded
> >> Import of duplicity.backends.giobackend Succeeded
> >> Import of duplicity.backends.hsibackend Succeeded
> >> Import of duplicity.backends.hubicbackend Succeeded
> >> Import of duplicity.backends.imapbackend Succeeded
> >> Import of duplicity.backends.lftpbackend Succeeded
> >> Import of duplicity.backends.localbackend Succeeded
> >> Import of duplicity.backends.mediafirebackend Succeeded
> >> Import of duplicity.backends.megabackend Succeeded
> >> Import of duplicity.backends.multibackend Succeeded
> >> Import of duplicity.backends.ncftpbackend Succeeded
> >> Import of duplicity.backends.onedrivebackend Succeeded
> >> Import of duplicity.backends.par2backend Succeeded
> >> Import of duplicity.backends.pydrivebackend Succeeded
> >> Import of duplicity.backends.rsyncbackend Succeeded
> >> Import of duplicity.backends.ssh_paramiko_backend Succeeded
> >> Import of duplicity.backends.ssh_pexpect_backend Succeeded
> >> Import of duplicity.backends.swiftbackend Succeeded
> >> Import of duplicity.backends.sxbackend Succeeded
> >> Import of duplicity.backends.tahoebackend Succeeded
> >> Import of duplicity.backends.webdavbackend Succeeded
> >> Reading globbing filelist /etc/azure_excludes.txt
> >> Main action: inc
> >> ================================================================================
> >> duplicity 0.7.10 (August 20, 2016)
> >> Args: /usr/bin/duplicity -v info --volsize 300 --gpg-options 
> >> --pinentry-mode loopback --exclude-filelist /etc/azure_excludes.txt --name 
> >> backup_linux --encrypt-key address@hidden --asynchronous-upload / 
> >> azure://linux
> >> Linux ccs.covici.com 4.4.27-gentoo #1 SMP PREEMPT Sun Oct 23 11:40:31 EDT 
> >> 2016 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
> >> /usr/lib/python-exec/python2.7/python2 2.7.12 (default, Sep 29 2016, 
> >> 18:15:31) 
> >> [GCC 4.9.3]
> >> ================================================================================
> >> Using temporary directory /tmp/duplicity-_oRmY1-tempdir
> >> Temp has 36320706560 available, backup will use approx 723517440.
> >> Local and Remote metadata are synchronized, no sync needed.
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161103T070100Z.to.20161104T070101Z.manifest.part
> >>  (2111)
> >> Found 9 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-full.20161015T074955Z.manifest
> >>  (206577452)
> >> Found 4526 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161015T074955Z.to.20161018T070058Z.manifest
> >>  (7752539)
> >> Found 12 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161018T070058Z.to.20161019T070100Z.manifest
> >>  (5117602)
> >> Found 12 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161019T070100Z.to.20161020T070056Z.manifest
> >>  (620795)
> >> Found 2 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161020T070056Z.to.20161021T070057Z.manifest
> >>  (652761)
> >> Found 1 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161021T070057Z.to.20161022T070058Z.manifest
> >>  (73273)
> >> Found 5 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161022T070058Z.to.20161023T070104Z.manifest
> >>  (42982)
> >> Found 9 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161023T070104Z.to.20161024T070103Z.manifest
> >>  (10695139)
> >> Found 4 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161024T070103Z.to.20161025T070059Z.manifest
> >>  (18076556)
> >> Found 10 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161025T070059Z.to.20161026T070100Z.manifest
> >>  (6217478)
> >> Found 14 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161026T070100Z.to.20161027T070108Z.manifest
> >>  (2647319)
> >> Found 25 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161027T070108Z.to.20161028T070109Z.manifest
> >>  (580454)
> >> Found 3 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161028T070109Z.to.20161029T070107Z.manifest
> >>  (51600)
> >> Found 3 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161029T070107Z.to.20161030T070132Z.manifest
> >>  (2882858)
> >> Found 12 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161030T070132Z.to.20161031T070100Z.manifest
> >>  (6249737)
> >> Found 23 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161031T070100Z.to.20161101T070102Z.manifest
> >>  (75366)
> >> Found 3 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161101T070102Z.to.20161102T070059Z.manifest
> >>  (55709)
> >> Found 2 volumes in manifest
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161102T070059Z.to.20161103T070100Z.manifest
> >>  (59930)
> >> Found 3 volumes in manifest
> >> Added incremental Backupset (start_time: Sat Oct 15 03:49:55 2016 / 
> >> end_time: Tue Oct 18 03:00:58 2016)
> >> Added incremental Backupset (start_time: Tue Oct 18 03:00:58 2016 / 
> >> end_time: Wed Oct 19 03:01:00 2016)
> >> Added incremental Backupset (start_time: Wed Oct 19 03:01:00 2016 / 
> >> end_time: Thu Oct 20 03:00:56 2016)
> >> Added incremental Backupset (start_time: Thu Oct 20 03:00:56 2016 / 
> >> end_time: Fri Oct 21 03:00:57 2016)
> >> Added incremental Backupset (start_time: Fri Oct 21 03:00:57 2016 / 
> >> end_time: Sat Oct 22 03:00:58 2016)
> >> Added incremental Backupset (start_time: Sat Oct 22 03:00:58 2016 / 
> >> end_time: Sun Oct 23 03:01:04 2016)
> >> Added incremental Backupset (start_time: Sun Oct 23 03:01:04 2016 / 
> >> end_time: Mon Oct 24 03:01:03 2016)
> >> Added incremental Backupset (start_time: Mon Oct 24 03:01:03 2016 / 
> >> end_time: Tue Oct 25 03:00:59 2016)
> >> Added incremental Backupset (start_time: Tue Oct 25 03:00:59 2016 / 
> >> end_time: Wed Oct 26 03:01:00 2016)
> >> Added incremental Backupset (start_time: Wed Oct 26 03:01:00 2016 / 
> >> end_time: Thu Oct 27 03:01:08 2016)
> >> Added incremental Backupset (start_time: Thu Oct 27 03:01:08 2016 / 
> >> end_time: Fri Oct 28 03:01:09 2016)
> >> Added incremental Backupset (start_time: Fri Oct 28 03:01:09 2016 / 
> >> end_time: Sat Oct 29 03:01:07 2016)
> >> Added incremental Backupset (start_time: Sat Oct 29 03:01:07 2016 / 
> >> end_time: Sun Oct 30 03:01:32 2016)
> >> Added incremental Backupset (start_time: Sun Oct 30 03:01:32 2016 / 
> >> end_time: Mon Oct 31 03:01:00 2016)
> >> Added incremental Backupset (start_time: Mon Oct 31 03:01:00 2016 / 
> >> end_time: Tue Nov  1 03:01:02 2016)
> >> Added incremental Backupset (start_time: Tue Nov  1 03:01:02 2016 / 
> >> end_time: Wed Nov  2 03:00:59 2016)
> >> Added incremental Backupset (start_time: Wed Nov  2 03:00:59 2016 / 
> >> end_time: Thu Nov  3 03:01:00 2016)
> >> Added incremental Backupset (start_time: Thu Nov  3 03:01:00 2016 / 
> >> end_time: Fri Nov  4 03:01:01 2016)
> >> Last inc backup left a partial set, restarting.
> >> Last full backup date: Sat Oct 15 03:49:55 2016
> >> Processing local manifest 
> >> /root/.cache/duplicity/backup_linux/duplicity-inc.20161103T070100Z.to.20161104T070101Z.manifest.part
> >>  (2111)
> >> Found 9 volumes in manifest
> >> RESTART: Volumes 6 to 9 failed to upload before termination.
> >>          Restarting backup at volume 6.
> >> Invalid data - SHA1 hash mismatch for file:
> >>  duplicity-inc.20161103T070100Z.to.20161104T070101Z.vol1.difftar.gpg
> >>  Calculated hash: da39a3ee5e6b4b0d3255bfef95601890afd80709
> >>  Manifest hash: dac7743b0440026f59280f6a6bd34283edc86be2
> >>
> >>
> >> So, the program just terminated without any other message.  How can I
> >> fix?
> >>
> >> Thanks in advance for any suggestions.
> >>
> >> -- 
> >> Your life is like a penny.  You're going to lose it.  The question is:
> >> How do
> >> you spend it?
> >>
> >>          John Covici
> >>          address@hidden
> >>
> >> _______________________________________________
> >> Duplicity-talk mailing list
> >> address@hidden
> >> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> > 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         address@hidden