Results 1 to 2 of 2

Thread: DUPLICITY: system clock issue

  1. #1
    Join Date
    Jul 2009
    Beans
    69
    Distro
    Ubuntu 10.04 Lucid Lynx

    Thumbs down DUPLICITY: system clock issue

    Hello forum.

    I'm currently facing this bug using DUPLICITY :

    Code:
    Local and Remote metadata are synchronized, no sync needed.
    Last inc backup left a partial set, restarting.
    Last full backup date: Sat Mar 19 14:40:11 2011
    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 messages above are displayed after a backup. This is slightly irritating, since it happens after a very long backup on a remote box.

    I tried a "cleanup", without success.

    Does anyone know how to fix this ? Is there some limitation to the use of DUPLICITY ?

  2. #2
    Join Date
    Feb 2010
    Location
    Land of Confusion
    Beans
    8,348
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: DUPLICITY: system clock issue

    Bump for move to General Help.
    Thank you for your contributions. "So long and thanks for the fish!"

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •