Your message dated Wed, 12 May 2010 17:50:19 +1000
with message-id <[email protected]>
and subject line Re: Bug#581260: duplicity: Fails with "AssertionError: time
not moving forward at appropriate pace - system clock issues?"
has caused the Debian Bug report #581260,
regarding duplicity: Fails with "AssertionError: time not moving forward at
appropriate pace - system clock issues?"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
581260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581260
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: duplicity
Version: 0.6.08b-1.1
Severity: normal
Hi.
I have the following error reported :
Info: Local and Remote metadata are synchronized, no sync needed.
Info: Last inc backup left a partial set, restarting.
Info: Last full backup date: Tue May 4 21:49:52 2010
Info: Traceback (most recent call last):
Info: File "/usr/bin/duplicity", line 1258, in <module>
Info: with_tempdir(main)
Info: File "/usr/bin/duplicity", line 1251, in with_tempdir
Info: fn()
Info: File "/usr/bin/duplicity", line 1233, in main
Info: incremental_backup(sig_chain)
Info: File "/usr/bin/duplicity", line 475, in incremental_backup
Info: assert dup_time.curtime != dup_time.prevtime, "time not moving forward at
appropriate pace - system clock issues?"
Info: AssertionError: time not moving forward at appropriate pace - system
clock issues?
Fatal: Duplicity failed.
Hope this helps.
Best regards,
P.S.: this version of duplicity is adapted from the Debian package, but there
have been reports of the same error upstream, so I guess it's not in my local
patches.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages duplicity depends on:
ii gnupg 1.4.10-2 GNU privacy guard - a free PGP rep
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii librsync1 0.9.7-7 rsync remote-delta algorithm libra
ii python 2.5.4-9 An interactive high-level object-o
ii python-central 0.6.14+nmu2 register and build utility for Pyt
ii python-pexpect 2.3-1 Python module for automating inter
duplicity recommends no packages.
Versions of packages duplicity suggests:
ii ncftp 2:3.2.2-1 A user-friendly and well-featured
ii python-boto 1.9b-2 Python interface to Amazon's Web S
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, 12 May 2010 05:53:15 +0200, Olivier Berger writes:
>Info: AssertionError: time not moving forward at
>appropriate pace - system clock issues?
sorry, but this is not a bug in duplicity.
as upstream (kenneth loafman) states authoritatively in
http://permalink.gmane.org/gmane.comp.sysutils.backup.duplicity.general/3945
this report indicates a time-related problem on your system, and
duplicity cannot and will not work in such a setup, full stop.
one possible culprit that i can think of would be running ntpdate from a
cronjob instead of using ntpd.
regards
az
--
+ Alexander Zangerl + DSA 42BD645D + (RSA 5B586291)
"You are in a maze of twisted sysadmins, all different."
-- Ben Aveling, in and about the scary.devil.monastery
signature.asc
Description: Digital Signature
--- End Message ---
