[Duplicity-talk] Re: Duplicity-talk Digest, Vol 82, Issue 5

[Joel Carter]

Thanks for the quick response, I'll take a look at that junk of code
and see if I can isolate the time.sleep() problem outside of
Duplicity.

Any think jump out at you with my Python install?

# python -v
# installing zipimport hook
import zipimport # builtin
# installed zipimport hook
# /usr/lib64/python2.4/site.pyc matches /usr/lib64/python2.4/site.py
import site # precompiled from /usr/lib64/python2.4/site.pyc
# /usr/lib64/python2.4/os.pyc matches /usr/lib64/python2.4/os.py
import os # precompiled from /usr/lib64/python2.4/os.pyc
import posix # builtin
# /usr/lib64/python2.4/posixpath.pyc matches /usr/lib64/python2.4/posixpath.py
import posixpath # precompiled from /usr/lib64/python2.4/posixpath.pyc
# /usr/lib64/python2.4/stat.pyc matches /usr/lib64/python2.4/stat.py
import stat # precompiled from /usr/lib64/python2.4/stat.pyc
import errno # builtin
# /usr/lib64/python2.4/UserDict.pyc matches /usr/lib64/python2.4/UserDict.py
import UserDict # precompiled from /usr/lib64/python2.4/UserDict.pyc
# /usr/lib64/python2.4/copy_reg.pyc matches /usr/lib64/python2.4/copy_reg.py
import copy_reg # precompiled from /usr/lib64/python2.4/copy_reg.pyc
# /usr/lib64/python2.4/types.pyc matches /usr/lib64/python2.4/types.py
import types # precompiled from /usr/lib64/python2.4/types.pyc
import japanese # directory /usr/lib64/python2.4/site-packages/japanese
# /usr/lib64/python2.4/site-packages/japanese/__init__.pyc matches
/usr/lib64/python2.4/site-packages/japanese/__init__.py
import japanese # precompiled from
/usr/lib64/python2.4/site-packages/japanese/__init__.pyc
import japanese.aliases # directory
/usr/lib64/python2.4/site-packages/japanese/aliases
# /usr/lib64/python2.4/site-packages/japanese/aliases/__init__.pyc
matches /usr/lib64/python2.4/site-packages/japanese/aliases/__init__.py
import japanese.aliases # precompiled from
/usr/lib64/python2.4/site-packages/japanese/aliases/__init__.pyc
import encodings # directory /usr/lib64/python2.4/encodings
# /usr/lib64/python2.4/encodings/__init__.pyc matches
/usr/lib64/python2.4/encodings/__init__.py
import encodings # precompiled from /usr/lib64/python2.4/encodings/__init__.pyc
# /usr/lib64/python2.4/codecs.pyc matches /usr/lib64/python2.4/codecs.py
import codecs # precompiled from /usr/lib64/python2.4/codecs.pyc
import _codecs # builtin
# /usr/lib64/python2.4/encodings/aliases.pyc matches
/usr/lib64/python2.4/encodings/aliases.py
import encodings.aliases # precompiled from
/usr/lib64/python2.4/encodings/aliases.pyc
# /usr/lib64/python2.4/warnings.pyc matches /usr/lib64/python2.4/warnings.py
import warnings # precompiled from /usr/lib64/python2.4/warnings.pyc
# /usr/lib64/python2.4/linecache.pyc matches /usr/lib64/python2.4/linecache.py
import linecache # precompiled from /usr/lib64/python2.4/linecache.pyc
# /usr/lib64/python2.4/encodings/utf_8.pyc matches
/usr/lib64/python2.4/encodings/utf_8.py
import encodings.utf_8 # precompiled from
/usr/lib64/python2.4/encodings/utf_8.pyc
Python 2.4.3 (#1, Sep  3 2009, 15:37:37)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-46)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
dlopen("/usr/lib64/python2.4/lib-dynload/readline.so", 2);
import readline # dynamically loaded from
/usr/lib64/python2.4/lib-dynload/readline.so
>>>

I compiled duplicity from source and it was working but then installed
a whole bunch of packages near when it broke. I will try recompiling.


Thanks, Joel.

On Thu, May 6, 2010 at 9:02 AM,  <address@hidden> wrote:
> Send Duplicity-talk mailing list submissions to
>       address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.nongnu.org/mailman/listinfo/duplicity-talk
> or, via email, send a message with subject or body 'help' to
>       address@hidden
>
> You can reach the person managing the list at
>       address@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Duplicity-talk digest..."
>
>
> Today's Topics:
>
>   1. AssertionError: time not moving forward at        appropriate pace -
>      system clock issues? (Joel Carter)
>   2. Re: AssertionError: time not moving forward       at      appropriate
>      pace - system clock issues? (Kenneth Loafman)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 6 May 2010 08:15:12 -0700
> From: Joel Carter <address@hidden>
> Subject: [Duplicity-talk] AssertionError: time not moving forward at
>        appropriate pace - system clock issues?
> To: address@hidden
> Message-ID:
>        <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1
>
> 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.
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 06 May 2010 10:55:55 -0500
> From: Kenneth Loafman <address@hidden>
> Subject: Re: [Duplicity-talk] AssertionError: time not moving forward
>        at      appropriate pace - system clock issues?
> To: Discussion of the backup program duplicity
>        <address@hidden>
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 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
>>
>
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 260 bytes
> Desc: OpenPGP digital signature
> Url : 
> http://lists.nongnu.org/archive/html/duplicity-talk/attachments/20100506/b828b489/signature.bin
>
> ------------------------------
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>
>
> End of Duplicity-talk Digest, Vol 82, Issue 5
> *********************************************
>