error: can't start new thread

Bug #1728720 reported by Václav Haisman
This bug report is a duplicate of:  Bug #1727653: error: can't start new thread. Edit Remove
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
New
Undecided
Unassigned
Déjà Dup
New
Undecided
Unassigned
deja-dup (Ubuntu)
New
Undecided
Unassigned
duplicity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Deja-dup ends up with the following error (possibly a duplicity issue?):

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

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: deja-dup 36.2-0ubuntu1
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.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Oct 30 22:16:00 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/deja-dup
InstallationDate: Installed on 2011-11-13 (2178 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to artful on 2017-10-28 (2 days ago)

Revision history for this message
Václav Haisman (vzeman79) wrote :
Revision history for this message
Václav Haisman (vzeman79) wrote :

The process seems to be stuck at this state for some time:

23574 ? SLl 35:08 deja-dup --backup --auto
24687 ? Ssl 4:30 \_ /usr/bin/python /usr/bin/duplicity restore --gio --file-to-restore=home/wilx/.cache/deja-dup/metadata --force ftp://wilx@10.0.0.3/wilx/backup.amber2 /home/wilx/.cache/deja-dup/metadata --verbosity=9 --gpg-options=--no-use-agent --archive-dir=/home/wilx/.cache/deja-dup --tempdir=/tmp --log-fd=19
24998 ? SL 0:00 \_ gpg --status-fd 11 --passphrase-fd 20 --logger-fd 9 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback --no-use-agent --decrypt
25001 ? SL 0:00 \_ gpg --status-fd 20 --passphrase-fd 24 --logger-fd 12 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback --no-use-agent --decrypt
25004 ? SL 0:01 \_ gpg --status-fd 24 --passphrase-fd 28 --logger-fd 21 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback --no-use-agent --decrypt
25007 ? SL 0:00 \_ gpg --status-fd 28 --passphrase-fd 32 --logger-fd 25 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback --no-use-agent --decrypt
25010 ? SL 0:00 \_ gpg --status-fd 32 --passphrase-fd 36 --logger-fd 29 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback --no-use-agent --decrypt
25013 ? SL 0:01 \_ gpg --status-fd 36 --passphrase-fd 40 --logger-fd 33 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback --no-use-agent --decrypt
25016 ? SL 0:00 \_ gpg --status-fd 40 --passphrase-fd 44 --logger-fd 37 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback --no-use-agent --decrypt
25019 ? SL 0:00 \_ gpg --status-fd 44 --passphrase-fd 48 --logger-fd 41 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback --no-use-agent --decrypt
25021 ? SL 0:00 \_ gpg --status-fd 48 --passphrase-fd 52 --logger-fd 45 --batch --no-tty --no-secmem-warning --pinentry-mode=loopback --no-use-agent --decrypt

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.