Duplicity

Assertion error "time not moving forward at appropriate pace"

Bug #579958 reported by Olivier Berger on 2010-05-13

116

This bug affects 16 people

Affects		Status	Importance	Assigned to	Milestone
	Duplicity	Fix Released	Medium	Unassigned	Duplicity 0.6.13
	duplicity (Debian)	Fix Released	Unknown	debbugs #581260
	duplicity (Ubuntu)	Fix Released	Medium	Unassigned
Nominated for Lucid by Rolf Leggewie

Bug Description

Duplicity fails with the following assertion error : "time not moving forward at appropriate pace"

See the corresponding logs in : https://bugs.launchpad.net/duplicity/+bug/502609/comments/13 (wrongly reported in another bug's comments IMHO).

Related branches

lp:ubuntu/oneiric/duplicity

Revision history for this message

Olivier Berger (olivierberger) wrote on 2010-05-13:

https://bugs.launchpad.net/debian/+bug/502609/comments/16 seems to suggest a fix, by deleting files from the local archive

Revision history for this message

Olivier Berger (olivierberger) wrote on 2010-05-13:

@Dirk Leinenbach (referring to your comment in https://bugs.launchpad.net/duplicity/+bug/502609/comments/16) :
Was this an attempt to re-start a previously failed backup ?

I suspect that the files in question that you've had to remove were left-over from that previous failed backup, maybe.

See also the thread on the ML : http://lists.nongnu.org/archive/html/duplicity-talk/2010-05/msg00013.html about this issue, btw.

Revision history for this message

Dirk Leinenbach (j-launchpad-dirkleinenbach-de) wrote on 2010-05-13:

yes and no

yes, the files were probably left-over from a failed backup attempt: I had some connectivity issues the days before which probably caused a backup attempt to fail

no, I wasn't (at least not intentionally) trying to re-start that backup attempt but instead I wanted to start a new incremental backup

Revision history for this message

Olivier Berger (olivierberger) wrote on 2010-05-13:

Maybe duplicity tries to restart in any case when you issue another incremental backup command... so yes in all cases ?

Bug Watch Updater (bug-watch-updater) on 2010-05-13

Changed in debian:
status:	Unknown → Fix Released

Revision history for this message

Dirk Leinenbach (j-launchpad-dirkleinenbach-de) wrote on 2010-05-13:

well, then yes in all cases ;)

Andreas Olsson (andol) on 2010-05-14

affects:	ubuntu → duplicity (Ubuntu)
affects:	debian → duplicity (Debian)

Kenneth Loafman (kenneth-loafman) on 2010-05-23

Changed in duplicity:
status:	New → Fix Committed
importance:	Undecided → Medium
milestone:	none → 0.6.09

Bug Watch Updater (bug-watch-updater) on 2010-05-23

Changed in duplicity (Debian):
status:	Fix Released → Confirmed

Milan Bouchet-Valat (nalimilan) on 2010-06-02

Changed in duplicity (Ubuntu):
importance:	Undecided → Medium
status:	New → Triaged

Kenneth Loafman (kenneth-loafman) on 2010-07-25

Changed in duplicity:
milestone:	0.6.09 → none
status:	Fix Committed → Fix Released

Revision history for this message

Michael Terry (mterry) wrote on 2010-07-27:

I just uploaded 0.6.09 to Ubuntu Maverick.

Changed in duplicity (Ubuntu):
status:	Triaged → Fix Released

Revision history for this message

Milan Bouchet-Valat (nalimilan) wrote on 2010-07-29:

Great, thanks!

Revision history for this message

Rodrigo Alvarez (rodrigo-alvarez-i) wrote on 2010-08-19:

I'm running 0.6.08b on Ubuntu Lucid and I'm finding this bug. Would you kindly upload 0.6.09 to Lucid's repository.

Revision history for this message

Michael Terry (mterry) wrote on 2011-03-26:

I'm still seeing this error if I cancel a backup then try backing up again. Clearing the cache solves it. Anyone else seeing it?

Revision history for this message

Michael Terry (mterry) wrote on 2011-03-29:

#10

I'm reopening this. I can consistently get this by cancelling an incremental backup. I will attach files to reproduce this error.

Changed in duplicity:
status:	Fix Released → Confirmed

Revision history for this message

Michael Terry (mterry) wrote on 2011-03-29:

#11

partial.tar.bz2 Edit (1.6 KiB, application/x-tar)

Put the files in cache/ in a duplicity cache directory with the right md5 sum or backup name. Then put the files in real/ in your backup location. No encryption.

You'll get the "time not moving forward error" until you clear out the cache.

I made these files by doing a simple small initial backup, then trying to do a larger incremental backup but cancelling it instead.

Kenneth Loafman (kenneth-loafman) on 2011-03-29

Changed in duplicity:
assignee:	nobody → Kenneth Loafman (kenneth-loafman)
milestone:	none → 0.6.13
status:	Confirmed → In Progress

Kenneth Loafman (kenneth-loafman) on 2011-03-29

Changed in duplicity:
assignee:	Kenneth Loafman (kenneth-loafman) → nobody
status:	In Progress → Fix Committed

Kenneth Loafman (kenneth-loafman) on 2011-04-02

Changed in duplicity:
status:	Fix Committed → Fix Released

Michael Terry (mterry) on 2011-04-04

Changed in duplicity (Ubuntu):
status:	Fix Released → Fix Committed
status:	Fix Committed → Triaged

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-04-04:

#12

This bug was fixed in the package duplicity - 0.6.13-0ubuntu1

---------------
duplicity (0.6.13-0ubuntu1) natty; urgency=low

  * Resync with Debian, no remaining changes
  * New upstream release
    - silent data corruption with checkpoint/restore (LP: #613244)
    - Assertion error "time not moving forward at appropriate pace"
      (LP: #579958)
  * debian/patches/04future.dpatch:
    - Dropped, applied upstream
-- Michael Terry <email address hidden> Sun, 03 Apr 2011 20:40:34 -0400

Changed in duplicity (Ubuntu):
status:	Triaged → Fix Released

Revision history for this message

Frederik Elwert (frederik-elwert) wrote on 2011-07-12:

#13

Are there plans to backport this fix to lucid? duplicity/déja-dup are one of the easiest/best backup tools for lucid, and it would be good to have it working there. I stumbled upon this bug with two machines running Lucid in our offices.

Bug Watch Updater (bug-watch-updater) on 2011-08-11