Assertion error "time not moving forward at appropriate pace"

Bug #579958 reported by Olivier Berger on 2010-05-13
This bug affects 16 people
Affects Status Importance Assigned to Milestone
duplicity (Debian)
Fix Released
duplicity (Ubuntu)
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 : (wrongly reported in another bug's comments IMHO).

Related branches

Olivier Berger (olivierberger) wrote : seems to suggest a fix, by deleting files from the local archive

Olivier Berger (olivierberger) wrote :

@Dirk Leinenbach (referring to your comment in :
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 : about this issue, btw.

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

Olivier Berger (olivierberger) wrote :

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

Changed in debian:
status: Unknown → Fix Released

well, then yes in all cases ;)

Andreas Olsson (andol) on 2010-05-14
affects: ubuntu → duplicity (Ubuntu)
affects: debian → duplicity (Debian)
Changed in duplicity:
status: New → Fix Committed
importance: Undecided → Medium
milestone: none → 0.6.09
Changed in duplicity (Debian):
status: Fix Released → Confirmed
Changed in duplicity (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Changed in duplicity:
milestone: 0.6.09 → none
status: Fix Committed → Fix Released
Michael Terry (mterry) wrote :

I just uploaded 0.6.09 to Ubuntu Maverick.

Changed in duplicity (Ubuntu):
status: Triaged → Fix Released
Milan Bouchet-Valat (nalimilan) wrote :

Great, thanks!

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.

Michael Terry (mterry) wrote :

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?

Michael Terry (mterry) wrote :

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
Michael Terry (mterry) wrote :

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.

Changed in duplicity:
assignee: nobody → Kenneth Loafman (kenneth-loafman)
milestone: none → 0.6.13
status: Confirmed → In Progress
Changed in duplicity:
assignee: Kenneth Loafman (kenneth-loafman) → nobody
status: In Progress → Fix Committed
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
Launchpad Janitor (janitor) wrote :

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

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.

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

I would also like this for Lucid.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.