> 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 10
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 receiv
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Log head.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/49893
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 -
https://launchpad.net/
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Cra
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
To ma
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)
F
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
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Cra
** 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 Ubuntu
Bugs, w
Can anyone reproduce this with the current version, 0.6.17??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
To manage notifications about this bug go
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
C
** Changed in: duplicity
Importance: Medium => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
To manage notifications about this bug go t
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
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 Ubuntu
Bugs, which is subscribed to Ubunt
** Changed in: duplicity
Milestone: 0.6.15 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
To manage notifications about this bug go to:
h
Thanks, Scott.
Another interesting data point is that this bug's original reporter was
using duplicity 0.5.18, right before checkpoint/restart support was
added. So this likely isn't a bug with that feature.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've only started using Deja-dup (and thus Duplicity) since I've been
running Ubuntu 11.04. I'm currently running duplicity-0.6.13, and have
only used an older version if such a version was once in the official
Natty repositories.
--
You received this bug notification because you are a member of
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
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 Ubuntu
Bugs, which is subscribed to Ub
I'm also experiencing this bug. I'm backing up to RackSpace via DéjàDup.
I don't know if this helps any, but I have DéjàDup configured to backup
daily and keep backups for "at least a month." Because my backup set is
large and my machine isn't always online, full backups take considerably
more tha
I know it's unlikely, but if anyone has a backup set that is exhibiting
this problem and can be shared with me, please let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash
This has happened with both Deja Dup (this bug) and base duplicity (bug
751178). And it's happened with the gio backend (multiple protocols)
and the ftp backend (bug 751178 again). So I doubt it's something Deja
Dup is doing or some bug with a specific backend silently not writing
its files.
The
** Changed in: deja-dup
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
To manage notifications about this bug go
If it's any help, the place where my backup was located is a debian machine
running samba, and I mounted it using cifs. I tried restoring older backups
but with the same error. It also didn't work when i tried to restore using
command-line duplicity, for obvious reasons. The laptop i backed up from
I can imagine how one might be missing if it was the last one being sent and
it never made it before a forced shutdown. But we handle that case.
The other possible issue is concurrency, but that's not likely. I can see
how one volume might go missing, but not 5.
...Ken
On Fri, Jul 8, 2011 at 1
Ken, when Jorgen talks about GNOME bookmarks, he's talking about using
Deja Dup and selecting a backup from a dropdown populated with GNOME
bookmarks.
I've been thinking about this bug, and I'm confused. It seems
relatively common, but I can't figure out how duplicity would leave gaps
in the back
** Changed in: duplicity
Milestone: 0.6.14 => 0.6.15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
To manage notifications about this bug go to:
** Changed in: duplicity
Milestone: 0.6.13 => 0.6.14
** Changed in: duplicity
Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
** Changed in: duplicity
Milestone: 0.6.12 => 0.6.13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
--
ubuntu-bugs mailing list
ubuntu-bugs@list
** Changed in: duplicity
Milestone: None => 0.6.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/498933
Title:
Crash when restoring data KeyError
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Hi,
When I use the normal FTP protocol and I enter a path it must first
change to before starting the backup, it refuses to change to that path.
So I decided to use a Gnome bookmark which seems to be a saved session
state of the current FTP login path and username. That works well with
sendig
What is a Gnome Bookmark and how do you back up to it? Did you use a
file:// URL as the destination, or ftp:// as the destination. Please be
aware that file:// has no retry semantics since it is targeted to the
local filesystem. It's possible that whatever is underneath a Gnome
Bookmark may be f
Hi,
I am also experiencing the same error. I did a full backup (encryped)
and wanted to check a restore today. I chose a different directory just
to see if the restored files would match the last incremental backup
that happened today.
/home/jorg is the home dir that is backed up, Downloads, temp
I can consistently reproduce something apparently similar with one of my
backups. Interestingly it happens after "processed volume 51 of 51",
but to judge by the filenames it was a long way from done restoring, and
there are a total of 76 increments in the full backup.
Writing bzr-explorer/.bzr/
** Changed in: duplicity
Milestone: None => 0.6.07
** Changed in: duplicity
Status: Won't Fix => Invalid
** Changed in: duplicity
Milestone: 0.6.07 => None
--
Crash when restoring data KeyError
https://bugs.launchpad.net/bugs/498933
You received this bug notification because you
Closing out deja-dup side of this bug until/if it resurfaces.
** Changed in: deja-dup (Ubuntu)
Status: New => Invalid
--
Crash when restoring data KeyError
https://bugs.launchpad.net/bugs/498933
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Closing out deja-dup side of this bug until/if it resurfaces.
** Changed in: deja-dup
Status: New => Invalid
--
Crash when restoring data KeyError
https://bugs.launchpad.net/bugs/498933
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I cannot reproduce this one at all. I'm closing as "Won't Fix" since LP
does not have the option "Can't Fix".
As to checking afterwards, that's what the verify command is intended to
do.
** Changed in: duplicity
Milestone: None => 0.6.07
** Changed in: duplicity
Importance: Critical => M
I restored my computer, reinstalled Deja Dup, reran the backup and
tested that it works (which it does now). So I don't know what went
wrong before, but perhaps at the end of the backup it should verify that
the backup actually worked?
--
Crash when restoring data KeyError
https://bugs.launchpad.
** Changed in: duplicity
Importance: Undecided => Critical
** Changed in: duplicity
Status: New => In Progress
--
Crash when restoring data KeyError
https://bugs.launchpad.net/bugs/498933
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Not really. As far as I know, this is the first time.
raccoonone wrote:
> k. Any idea what caused this in the first place?
>
--
Crash when restoring data KeyError
https://bugs.launchpad.net/bugs/498933
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
k. Any idea what caused this in the first place?
--
Crash when restoring data KeyError
https://bugs.launchpad.net/bugs/498933
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
It may be possible to remove volume 15 from the manifest and go on from
there. You'll need to save a copy of the manifest, edit the file in
place, and remove the lines:
Volume 15:
StartingPath home/christopher/.mozilla/firefox/lm8fky5t.default/XPC.mfasl
EndingPath home/christopher/C
Hmm, there's no vol15. Did something go wrong with the backup, and can I
recover the rest of my files somehow?
--
Crash when restoring data KeyError
https://bugs.launchpad.net/bugs/498933
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I was wrong, it looks like a volume (# 15) is missing. Could you verify
that there is indeed a "duplicity-full.*-vol15.difftar.gpg" in your
collection.
--
Crash when restoring data KeyError
https://bugs.launchpad.net/bugs/498933
You received this bug notification because you are a member of Ubun
Here you go. Let me know if there are any other logs that you need.
** Attachment added: "deja-dup-logs.tar"
http://launchpadlibrarian.net/37024402/deja-dup-logs.tar
--
Crash when restoring data KeyError
https://bugs.launchpad.net/bugs/498933
You received this bug notification because you are
raccoonone, you can get the log from Deja Dup by running the following:
DEJA_DUP_DEBUG=1 deja-dup > /tmp/deja-dup.log
cat /tmp/deja-dup.log | head -n 200 > /tmp/deja-dup.head
cat /tmp/deja-dup.log | tail -n 200 > /tmp/deja-dup.tail
And attaching deja-dup.head and deja-dup.tail.
For the manife
It looks like there may be an issue with the Manifest. The error says
that volume 15 is not in the list, but it should be.
raccoonone, please attach the manifest (decrypted) to this bug report,
also, I need more info from the log. Please run with -v9 and attach the
first 200 lines and the last 2
Ken, raccoonone's using duplicity 0.5.18-0ubuntu1. I haven't seen this
stack trace before.
--
Crash when restoring data KeyError
https://bugs.launchpad.net/bugs/498933
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Yikes. This looks like it's crashing inside duplicity, the command line
backup tool that does the heavy lifting behind the scenes.
** Changed in: deja-dup (Ubuntu)
Importance: Undecided => Critical
** Also affects: deja-dup
Importance: Undecided
Status: New
** Changed in: deja-dup
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/37006149/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/37006150/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/37006151/ProcStatus.txt
** Attachm
61 matches
Mail list logo
