Hello,

Today I hit the same problem as in bug #1722454, MemoryError in
manifest.py. I am on Ubuntu 17.10 with duplicity 0.7.12-1ubuntu1. I also
found a bugreport in Debian that seems to be the same thing:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881021

Here is my backtrace:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1546, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1540, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1391, in main
    do_backup(action)
  File "/usr/bin/duplicity", line 1416, in do_backup
    globals.archive_dir).set_values()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710, 
in set_values
    self.get_backup_chains(partials + backend_filename_list)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 836, 
in get_backup_chains
    add_to_sets(f)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 824, 
in add_to_sets
    if set.add_filename(filename):
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101, 
in add_filename
    self.set_manifest(filename)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 148, 
in set_manifest
    self.set_files_changed()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128, 
in set_files_changed
    mf = self.get_manifest()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
    return self.get_local_manifest()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
    return manifest.Manifest().from_string(manifest_buffer)
  File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 207, in 
from_string
    self.files_changed = list(map(parse_fileinfo, match.group(3).split('\n')))
MemoryError


** Bug watch added: Debian Bug tracker #881021
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881021

-- 
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/1727653

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  ------------------

  Failed with an unknown error.

  Traceback (most recent call last):
    File "/usr/bin/duplicity", line 1546, in <module>
      with_tempdir(main)
    File "/usr/bin/duplicity", line 1540, in with_tempdir
      fn()
    File "/usr/bin/duplicity", line 1391, in main
      do_backup(action)
    File "/usr/bin/duplicity", line 1468, in do_backup
      restore(col_stats)
    File "/usr/bin/duplicity", line 731, in restore
      restore_get_patched_rop_iter(col_stats)):
    File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
      for ropath in rop_iter:
    File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
      for patch_seq in collated:
    File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
      setrorps(overflow, elems)
    File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
      elems[i] = iter_list[i].next()
    File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
      for path in path_iter:
    File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
      tarinfo_list = [tar_iter.next()]
    File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
      self.set_tarfile()
    File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
      self.current_fp = self.fileobj_iter.next()
    File "/usr/bin/duplicity", line 768, in get_fileobj_iter
      manifest.volume_info_dict[vol_num])
    File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
      fileobj = tdp.filtered_open_with_delete("rb")
    File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
      fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
    File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
      return gpg.GPGFile(False, self, gpg_profile)
    File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
      'logger': self.logger_fp})
    File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
      create_fhs, attach_fhs)
    File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
      process.thread.start()
    File "/usr/lib/python2.7/threading.py", line 736, in start
      _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --------------

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to