[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] AssertionError: time not moving forward at appropri
From: |
Olivier Berger |
Subject: |
Re: [Duplicity-talk] AssertionError: time not moving forward at appropriate pace - system clock issues? |
Date: |
Thu, 13 May 2010 15:25:43 +0200 |
Le mercredi 12 mai 2010 à 08:12 +0200, Olivier Berger a écrit :
> Hi.
>
> Le jeudi 06 mai 2010 à 08:15 -0700, Joel Carter a écrit :
> > Hello all.
> >
> > Any tips on diagnosing what I have going on here?
> >
> SNIP
>
> > AssertionError: time not moving forward at appropriate pace - system
> > clock issues?
> >
>
> For the records, there's also a similar report here :
> https://bugs.launchpad.net/duplicity/+bug/502609/comments/13 and
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581260 (I've been
> myself hit by that same bug).
>
AFYI, about that issue, I have opened another ticket in LP :
https://bugs.launchpad.net/duplicity/+bug/579958 (the comments cited
above were made for another problem actually).
> It seems to me the common element is that message:
> Info: Last inc backup left a partial set, restarting.
>
> I worked around it by issueing a cleanup command,
>
Another user reported in LP that he solved the same problem by removing
2 files from the local archive :
"It turned out that the problem was caused by two .part files in
duplicities local archive:
duplicity-inc.20100501T230102Z.to.20100502T230102Z.manifest.part
duplicity-new-signatures.20100501T230102Z.to.20100502T230102Z.sigtar.part
deleting these files solved the problem for me"
Ain't there any bug, or is this really caused by clock issues... :-/
Hope this helps.
Best regards,
--
Olivier BERGER <address@hidden>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)