[Duplicity-talk] duplicity has clock issues and stopped working

[Yves Goergen]

Hi,

since my last system reboot, I get this message from duplicity when it's
supposed to do a backup. No matter whether full or incremental.

> Traceback (most recent call last):
>   File "/usr/bin/duplicity", line 1239, in <module>
>     with_tempdir(main)
>   File "/usr/bin/duplicity", line 1232, in with_tempdir
>     fn()
>   File "/usr/bin/duplicity", line 1214, in main
>     incremental_backup(sig_chain)
>   File "/usr/bin/duplicity", line 474, in incremental_backup
>     assert dup_time.curtime != dup_time.prevtime, "time not moving forward at 
> appropriate pace - system clock issues?"
> AssertionError: time not moving forward at appropriate pace - system clock 
> issues?

The clock is fine. It's NTP-synchronised as always. So what's the matter
here? How can I make it work again?

Using Ubuntu 10.4 and duplicity 0.6.08b. No changes to that for months.

-- 
Yves Goergen "LonelyPixel" <address@hidden>
Visit my web laboratory at http://beta.unclassified.de