Debugging the Python process of Duplicity shows no polling or reading
from appropriate number of pipes:
* 1 Thread 0x7f7f510d0740 (LWP 19797) 0x00007f7f50ce9f96 in
futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0,
futex_word=0x559f3d5e48f0)
at ../sysdeps/unix/sysv/linux/futex-internal.h:205
2 Thread 0x7f7f4d9b0700 (LWP 19801) 0x00007f7f50a01951 in __GI___poll
(fds=0x559f3d517d30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
3 Thread 0x7f7f469fd700 (LWP 19802) 0x00007f7f50a01951 in __GI___poll
(fds=0x559f3d5290a0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
4 Thread 0x7f7f461fc700 (LWP 19960) 0x00007f7f50ceba4a in __waitpid
(pid=19959, stat_loc=0x7f7f461fb534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
5 Thread 0x7f7f3ffff700 (LWP 19962) 0x00007f7f50ceba4a in __waitpid
(pid=19961, stat_loc=0x7f7f3fffe534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
6 Thread 0x7f7f3f7fe700 (LWP 19965) 0x00007f7f50ceba4a in __waitpid
(pid=19964, stat_loc=0x7f7f3f7fd534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
7 Thread 0x7f7f3effd700 (LWP 19967) 0x00007f7f50ceba4a in __waitpid
(pid=19966, stat_loc=0x7f7f3effc534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
8 Thread 0x7f7f3e7fc700 (LWP 19969) 0x00007f7f50ceba4a in __waitpid
(pid=19968, stat_loc=0x7f7f3e7fb534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
9 Thread 0x7f7f3dffb700 (LWP 19971) 0x00007f7f50ceba4a in __waitpid
(pid=19970, stat_loc=0x7f7f3dffa534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
10 Thread 0x7f7f3d7fa700 (LWP 19973) 0x00007f7f50ceba4a in __waitpid
(pid=19972, stat_loc=0x7f7f3d7f9534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
11 Thread 0x7f7f3cff9700 (LWP 19975) 0x00007f7f50ceba4a in __waitpid
(pid=19974, stat_loc=0x7f7f3cff8534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
12 Thread 0x7f7f2bfff700 (LWP 19977) 0x00007f7f50ceba4a in __waitpid
(pid=19976, stat_loc=0x7f7f2bffe534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
13 Thread 0x7f7f2b7fe700 (LWP 19979) 0x00007f7f50ceba4a in __waitpid
(pid=19978, stat_loc=0x7f7f2b7fd534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
14 Thread 0x7f7f2affd700 (LWP 19981) 0x00007f7f50ceba4a in __waitpid
(pid=19980, stat_loc=0x7f7f2affc534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
15 Thread 0x7f7f2a7fc700 (LWP 19983) 0x00007f7f50ceba4a in __waitpid
(pid=19982, stat_loc=0x7f7f2a7fb534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
16 Thread 0x7f7f29ffb700 (LWP 19985) 0x00007f7f50ceba4a in __waitpid
(pid=19984, stat_loc=0x7f7f29ffa534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
17 Thread 0x7f7f297fa700 (LWP 19988) 0x00007f7f50ceba4a in __waitpid
(pid=19987, stat_loc=0x7f7f297f9534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
--
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 deja-dup package in Ubuntu:
Confirmed
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 : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
