Deja-Dup fails with "Failed with an unknown error" (Memory Error)

Bug #1738187 reported by Chris Sharp on 2017-12-14
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Déjà Dup

Bug Description

Deja-Dup fails with "Failed with an unknown error" (Memory Error)

Using Deja-Dup 37.0/Duplicity 0.7.15 on Fedora 27. It fails right after boot just after receiving the "Starting Scheduled Backup" message with "Failed with an unknown error" and the following traceback:

Traceback (innermost last):
  File "/usr/bin/duplicity", line 1559, in <module>
  File "/usr/bin/duplicity", line 1545, in with_tempdir
  File "/usr/bin/duplicity", line 1394, in main
  File "/usr/bin/duplicity", line 1527, in do_backup
  File "/usr/bin/duplicity", line 669, in incremental_backup
  File "/usr/bin/duplicity", line 430, in write_multivol
  File "/usr/lib64/python2.7/site-packages/duplicity/", line 385, in GPGWriteFile
    data =
  File "/usr/lib64/python2.7/site-packages/duplicity/", line 523, in next
    result = self.process(
  File "/usr/lib64/python2.7/site-packages/duplicity/", line 218, in get_delta_iter
    (new_path, sig_path, sigTarFile))
  File "/usr/lib64/python2.7/site-packages/duplicity/", line 38, in check_common_error
    return function(*args)
  File "/usr/lib64/python2.7/site-packages/duplicity/", line 139, in get_delta_path
    delta_path.setfileobj(librsync.DeltaFile(old_sigfp, newfp))
  File "/usr/lib64/python2.7/site-packages/duplicity/", line 156, in __init__
    sig_string =
  File "/usr/lib64/python2.7/", line 829, in read
    buf +=
  File "/usr/lib64/python2.7/", line 743, in read
    return self.readnormal(size)
  File "/usr/lib64/python2.7/", line 758, in readnormal
    return self.__read(size)
  File "/usr/lib64/python2.7/", line 748, in __read
    buf =
  File "/usr/lib64/python2.7/", line 268, in read
  File "/usr/lib64/python2.7/", line 320, in _read
    self._add_read_data( uncompress )
  File "/usr/lib64/python2.7/", line 338, in _add_read_data
    self.extrabuf = self.extrabuf[offset:] + data

lsb_release -d:
Description: Fedora release 27 (Twenty Seven)

rpm -q deja-dup duplicity:

So far I'm unable to reproduce the problem manually with DEJA_DUP_DEBUG on as requested.

Chris Sharp (chrissharp123) wrote :
ausboffin (sdanaesthesia) wrote :

I have a similar problem, I get the same Memory Error at the end. I have fresh install of ubuntu 17.10, using an external hard drive with previous backups on it.

Tim Way (tim.way) wrote :

This bug has plagued me for a while. I'm backing up to a remote system via SSH. Fedora 27 with packages:

$ rpm -q deja-dup duplicity

Vej (vej) wrote :

Hello Tim and ausboffin.

Are you also unable to reproduce this bug with the following command-line?

DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log

Please set state back to Confirmed after answering!



Changed in deja-dup:
status: New → Confirmed
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for Déjà Dup because there has been no activity for 60 days.]

Changed in deja-dup:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers