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

[edgar . soldin]

just a wild guess. If your using an older python, maybe recent 2.6 does 
it for you?

also there was this change (2nd wild guess)
http://bazaar.launchpad.net/~duplicity-team/duplicity/0.6-series/revision/643
you could manually edit 'duplicity/dup_time.py' and check if it helps

.. ede

On 06.05.2010 17:55, Kenneth Loafman wrote:
> No changes in a long while to this piece of code:
>      if dup_time.curtime == dup_time.prevtime:
>          time.sleep(2)
>          dup_time.setcurtime()
>          assert dup_time.curtime != dup_time.prevtime, "time not moving \
>                 forward at appropriate pace - system clock issues?"
>
> Either time.sleep() is not working on your system, or time in general is
> not getting updated.  Either way, duplicity will not run because time is
> not progressing.  Running at this point would screw up way too much.
>
> ...Ken
>
> Joel Carter wrote:
> > 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.
> >
> >
> > _______________________________________________
> > Duplicity-talk mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk