I received a pretty similar error and thought I'd share my workaround.
It may be OT but people are bound to come across this bug when they
google.
The process would look like the backup was working (and for < 200MB and
a small number of files it did) - but larger folders would do up to 4
This bug was fixed in the package duplicity - 0.7.17-0ubuntu1
---
duplicity (0.7.17-0ubuntu1) bionic; urgency=medium
* New upstream bug-fix release
- Reverts a new feature that required too much memory, causing
OOM crashes (LP: #1730451)
-- Michael Terry
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1730451
Title:
MemoryError while verifying backup
Status in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: duplicity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
** Changed in: duplicity
Status: In Progress => Fix Committed
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
Also, deja-dup seems to run the "cleanup" command when it tries to do a
backup after failing. So this list is after the cleanup is done.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
Duplicity is run by deja-dup in my case:
python2 /usr/bin/duplicity --exclude=/mnt/Backup/duplicity
--include=/home/ocrete/.cache/deja-dup/metadata
--exclude=/home/ocrete/.ccache --exclude=/home/ocrete/.cache
--exclude=/home/ocrete/Videos --exclude=/home/ocrete/.local/share/Trash
** Changed in: duplicity
Milestone: 0.8.00 => 0.7.17
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1730451
Title:
MemoryError while verifying backup
Status in Duplicity:
In
- Please post the duplicity command line.
- Please do an 'ls -l' or equivalent of the backup target directory and
add as an attachment to this bug report. (see green + at bottom of
display).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Here is a slightly different traceback
Traceback (innermost last):
File "/usr/bin/duplicity", line 1559, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1545, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1394, in main
do_backup(action)
File "/usr/bin/duplicity",
I get the same error running against this one.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1730451
Title:
MemoryError while verifying backup
Status in Duplicity:
In Progress
Is this the backup causing the error reported?
If not, please run against that one.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1730451
Title:
MemoryError while verifying
Found 0 secondary backup chains.
Found primary backup chain with matching signature chain:
-
Chain start time: Fri Jan 5 18:45:00 2018
Chain end time: Wed Jan 17 16:44:04 2018
Number of contained backup sets: 2
Total number of contained volumes: 1741
Type of backup set:
Also, would you please provide the duplicity command line for the
incremental?
** Changed in: duplicity
Milestone: None => 0.8.00
** Changed in: duplicity
Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman)
** Changed in: duplicity
Importance: Undecided => High
** Changed
OK, sounds like the distro is keeping up. I like that.
One way to find out how many incrementals you have is "--collection-
status", like so:
$ duplicity --collection-status
and then counting the number of incrementals for the current backup. As
a rule of thumb, you should have fewer that 30
For some reason, a manually triggered backup from deja-dup worked this
time, and it did an incremental backup. I'm not sure what changed, as it
had failed multiple times today.
- When you upgraded to 0.7.15, did you remove the distro's version?
I use the distro's package (Fedora has 0.7.15)
-
@Olivier,
- When you upgraded to 0.7.15, did you remove the distro's version?
- How much memory do you have? Is it the same as previous?
- How long of an incremental change list do you have?
- Have you tried making a full backup?
On Wed, Jan 17, 2018 at 2:22 PM, Olivier Crête
This isn't a duplicate of the previous, I can reproduce the same exact
stack trace with 0.7.15 when trying to make a backup from deja-dup.
Traceback (innermost last):
File "/usr/bin/duplicity", line 1559, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1545, in with_tempdir
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
** This bug has been marked a duplicate of bug 1720159
Cannot allocate memory with large manifest file since 0.7.03
--
You received this bug notification because you are a member of Desktop
Packages,
19 matches
Mail list logo
