Gentoo Archives: gentoo-portage-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] dead emerge processes and/or lockfiles
Date: Mon, 25 Apr 2016 00:09:54
Message-Id: 571D604C.9020704@gentoo.org
In Reply to: Re: [gentoo-portage-dev] dead emerge processes and/or lockfiles by Joshua Kinard
1 On 04/24/2016 04:50 PM, Joshua Kinard wrote:
2 > On 01/18/2016 07:37, Joshua Kinard wrote:
3 >> On 01/17/2016 15:01, Zac Medico wrote:
4 >>> On 01/17/2016 09:06 AM, Brian Dolbec wrote:
5 >>>>
6 >>>> I've read in several forum posts lately about emerge not running and
7 >>>> the problem comes down to dead emerge processes and remaining lockfiles.
8 >>>>
9 >>>> Perhaps we should make an emaint module to search for and fix these.
10 >>>> It should be easy enough.
11 >>>
12 >>> It would be nicer if we fixed whatever issue(s) cause the emerge
13 >>> processes to hang up. How would the emaint module distinguish a "good"
14 >>> emerge process from a "bad" one? I suppose you could strace it to see if
15 >>> it has any activity.
16 >>>
17 >>
18 >> I've been playing around with Gentoo/FreeBSD and have been noticing that emerge
19 >> is leaving orphaned processes behind on that platform. Seems to be
20 >> ecompressdir getting hung up. emerge itself just moves on, but after I
21 >> accumulated ~5 of those stuck ecompressdir processes in a single run, I kill
22 >> -9'ed them all. Didn't see side-effects similar to what's described in the
23 >> original post, but the way to detect this issue might be to look for orphaned
24 >> children processes lacking a parent PID, then reap them.
25 >
26 >
27 > Updating my FreeBSD VM again, I captured one of the error messages that's
28 > leading to these orphaned ecompressdir processes:
29 >
30 > /usr/lib/portage/python3.5/ebuild-helpers/ecompressdir: cannot make pipe for
31 > process substitution: File exists
32 > /usr/lib/portage/python3.5/ebuild-helpers/ecompressdir: line 72:
33 > /ramfs/portage/sys-freebsd/boot0-10.3/temp/sh-np-1865519000: ambiguous redirect
34 > ecompressdir: bzip2 -9 /usr/share/man
35 > * The ebuild phase 'install' with pid 32075 appears to have left an orphan
36 > * process running in the background.
37 >
38 >
39 > And a second one:
40 > /ramfs/portage/._portage_reinstall_.pesqhjhn/bin/ebuild-helpers/ecompressdir:
41 > cannot make pipe for process substitution: File exists
42 > /ramfs/portage/._portage_reinstall_.pesqhjhn/bin/ebuild-helpers/ecompressdir:
43 > line 72: /ramfs/portage/sys-apps/grep-2.25/temp/sh-np-474708936: ambiguous redirect
44 > ecompressdir: bzip2 -9 /usr/share/man
45 > ecompressdir: bzip2 -9 /usr/share/info
46 > ecompressdir: bzip2 -9 /usr/share/doc
47 > * The ebuild phase 'install' with pid 60185 appears to have left an orphan
48 > * process running in the background.
49 >
50 > Not sure the exact cause. Any additional info I can provide?
51 >
52 > --J
53
54 Looks like a problem with bash. Make sure your bash has the fix for this
55 issue:
56
57 https://bugs.gentoo.org/show_bug.cgi?id=447810
58
59 What version of bash is it? Maybe try some other versions.
60 --
61 Thanks,
62 Zac

Replies

Subject Author
Re: [gentoo-portage-dev] dead emerge processes and/or lockfiles Joshua Kinard <kumba@g.o>