[Duplicity-talk] AssertionError: time not moving forward at appropriate pace - system clock issues?

[Joel Carter]

Hello all.

Any tips on diagnosing what I have going on here?

#  export PASSPHRASE=$(cat /root/DUPLICITY_PASSPHRASE) ; export
AWS_ACCESS_KEY_ID=$(cat /root/AWS_ACCESS_KEY_ID) ; export
AWS_SECRET_ACCESS_KEY=$(cat /root/AWS_SECRET_ACCESS_KEY) ;
NAME=`hostname -s` ; duplicity --exclude-filelist
/root/DUPLICITY_EXCLUDES full /
s3+http://$AWS_ACCESS_KEY_ID.duplicity/$NAME/
Reading filelist /root/DUPLICITY_EXCLUDES
Sorting filelist /root/DUPLICITY_EXCLUDES
Local and Remote metadata are synchronized, no sync needed.
Last inc backup left a partial set, restarting.
Last full backup date: Wed Apr 21 01:23:41 2010
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1239, in ?
    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?

I've got ntpd running and 0.6.08b:

# ntpstat
synchronised to NTP server (69.164.197.199) at stratum 3
   time correct to within 60 ms
   polling server every 1024 s

# duplicity --version
duplicity 0.6.08b

This is a Linode XEN VPS, any change that could have implications?

Thanks, Joel.