> The file list coming back from the remote is truncated [...]
You are absolutely right. I have WD My Cloud Mirror Gen 2 device and I
used FTP to store the backups there. It turns out the Pro-FTPd that it
uses only returns 1 lines for directory listing command and my
backups have grown beyond
OK, this is an old bug. The file list coming back from the remote is
truncated, however, I can clearly see vol43 in the list for
the 20171228T132324Z backup. Very confusing.
Would you look on the remote manually and compare the number of files? I'm
sure it is higher.
On Sun, Apr 1, 2018 at
Here is the result of `grep -C 10 "vol43\." deja-dup.log`. It is
compressed because it is otherwise 5 MiB.
** Attachment added: "result of `grep -C 10 "vol43\." deja-dup.log`"
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/498933/+attachment/5098011/+files/vol43.txt.xz
--
You
Please zip and post the entire log file if possible. If not possible,
please do do the following:
$ grep -C 10 "vol43\." YourLogFile
and attach the results.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
Log head.
** Attachment added: "Log head."
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/498933/+attachment/5097883/+files/deja-dup-log.head.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
Log head.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
Status in Déjà Dup:
Invalid
Status in Duplicity:
Confirmed
Status in
This is a tail of log:
DUPLICITY: DEBUG 1
DUPLICITY: . Found manifest volume 7529
DUPLICITY: DEBUG 1
DUPLICITY: . Found manifest volume 7530
DUPLICITY: DEBUG 1
DUPLICITY: . Found manifest volume 7531
DUPLICITY: INFO 1
DUPLICITY: . Found 7531 volumes in manifest
DUPLICITY: DEBUG 1
DUPLICITY: .
I am seeing this too. It happened first time after I started backups
from scratch after several weeks. It keeps occurring every day now.
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
Please upgrade to the 0.7.15 version of duplicity. This will assure
that any bugs fixed since the 0.7.12 release are available and may fix
your issue.
There are three options:
* Release tarball Install - https://launchpad.net/duplicity/+download
* Daily duplicity builds -
Setting back to confirmed because Kenneths question from comment #36 is
implicitly answered in comment #38.
** Changed in: duplicity
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
[Expired for Duplicity because there has been no activity for 60 days.]
** Changed in: duplicity
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
This seems to have helped me (clearing the cache):
mv ~/.cache/duplicity ~/.cache/duplicity.old
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring
It may or may not be related, but before seeing this bug, I had run
restore in a loop on different times, asynchronously, that is to say I
used:
for x in `seq 10 15`
duplicity --time {$x}D ... &
Note the ampersand, I forked them to a background process.
THEN on top of that I hit CTRL-C to force
I just had this bug on Ubuntu 17.10, duplicity 0.7.12
```
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
[Expired for Duplicity because there has been no activity for 60 days.]
** Changed in: duplicity
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
** Changed in: duplicity
Status: In Progress = Incomplete
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) = (unassigned)
** Changed in: duplicity
Importance: Critical = Medium
--
You received this bug notification because you are a member of Desktop
Can anyone reproduce this with the current version, 0.6.17??
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
Status in Déjà Dup
Closing deja-dup task, as this has been reported with just duplicity
alone.
** Changed in: deja-dup
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
D. Grady, your problem might be the same as mine, which is reported in
Bug #881727. It might be an issue separate from the one in this bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
My problem is definitely what you reported, megari, based on your much
fuller information provided. Not sure if it's the same bug or not.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
** Changed in: duplicity
Importance: Medium = Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
Status in Déjà Dup Backup
Ubuntu 10.04 LTS server
Duplicity 0.6.16 from PPA
--no-encryption to ssh storage server
backup runs fine.
Verify action (need to give --no-encryption as well) fails with KeyError: 1
every time for every backup set (there are about 20), some with multiple
volumes, some with only a single volume.
** Attachment added: .manifest file
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/498933/+attachment/2433661/+files/duplicity-full.20110916T182544Z.manifest
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in
Just a note, in 0.6.16, there will be some code to detect when this
happens as it happens, so hopefully there won't be any surprises at
resume time. We're still not sure of the root cause.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: duplicity
Milestone: 0.6.15 = None
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
Status in Déjà Dup Backup
Trying to reproduce this bug, but no luck. Could all of you that have
it verify what version of duplicity is causing the problem? Does the
problem occur with the latest version of duplicity?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Version information for this bug is hard to come by, since the useful
bit is the version that was actually used for the backup. But in bug
804484, the user implies that they backed up in Ubuntu 10.10 before
moving to (and trying to restore on) Ubuntu 11.04.
So that would mean duplicity 0.6.10 is
27 matches
Mail list logo
