From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] dead emerge processes and/or lockfiles
Date: Sun, 24 Apr 2016 20:21:24 -0400 [thread overview]
Message-ID: <571D6304.1080004@gentoo.org> (raw)
In-Reply-To: <571D604C.9020704@gentoo.org>
On 04/24/2016 20:09, Zac Medico wrote:
> On 04/24/2016 04:50 PM, Joshua Kinard wrote:
>> On 01/18/2016 07:37, Joshua Kinard wrote:
>>> On 01/17/2016 15:01, Zac Medico wrote:
>>>> On 01/17/2016 09:06 AM, Brian Dolbec wrote:
>>>>>
>>>>> I've read in several forum posts lately about emerge not running and
>>>>> the problem comes down to dead emerge processes and remaining lockfiles.
>>>>>
>>>>> Perhaps we should make an emaint module to search for and fix these.
>>>>> It should be easy enough.
>>>>
>>>> It would be nicer if we fixed whatever issue(s) cause the emerge
>>>> processes to hang up. How would the emaint module distinguish a "good"
>>>> emerge process from a "bad" one? I suppose you could strace it to see if
>>>> it has any activity.
>>>>
>>>
>>> I've been playing around with Gentoo/FreeBSD and have been noticing that emerge
>>> is leaving orphaned processes behind on that platform. Seems to be
>>> ecompressdir getting hung up. emerge itself just moves on, but after I
>>> accumulated ~5 of those stuck ecompressdir processes in a single run, I kill
>>> -9'ed them all. Didn't see side-effects similar to what's described in the
>>> original post, but the way to detect this issue might be to look for orphaned
>>> children processes lacking a parent PID, then reap them.
>>
>>
>> Updating my FreeBSD VM again, I captured one of the error messages that's
>> leading to these orphaned ecompressdir processes:
>>
>> /usr/lib/portage/python3.5/ebuild-helpers/ecompressdir: cannot make pipe for
>> process substitution: File exists
>> /usr/lib/portage/python3.5/ebuild-helpers/ecompressdir: line 72:
>> /ramfs/portage/sys-freebsd/boot0-10.3/temp/sh-np-1865519000: ambiguous redirect
>> ecompressdir: bzip2 -9 /usr/share/man
>> * The ebuild phase 'install' with pid 32075 appears to have left an orphan
>> * process running in the background.
>>
>>
>> And a second one:
>> /ramfs/portage/._portage_reinstall_.pesqhjhn/bin/ebuild-helpers/ecompressdir:
>> cannot make pipe for process substitution: File exists
>> /ramfs/portage/._portage_reinstall_.pesqhjhn/bin/ebuild-helpers/ecompressdir:
>> line 72: /ramfs/portage/sys-apps/grep-2.25/temp/sh-np-474708936: ambiguous redirect
>> ecompressdir: bzip2 -9 /usr/share/man
>> ecompressdir: bzip2 -9 /usr/share/info
>> ecompressdir: bzip2 -9 /usr/share/doc
>> * The ebuild phase 'install' with pid 60185 appears to have left an orphan
>> * process running in the background.
>>
>> Not sure the exact cause. Any additional info I can provide?
>>
>> --J
>
> Looks like a problem with bash. Make sure your bash has the fix for this
> issue:
>
> https://bugs.gentoo.org/show_bug.cgi?id=447810
>
> What version of bash is it? Maybe try some other versions.
Latest version in ~arch, bash-4.3_p42-r2.
Doesn't appear to be completely tied to FreeBSD, either, as there's this
unanswered topic on the forums from Nov 2015:
https://forums-lb.gentoo.org/viewtopic-t-1032574.html?sid=5d7566d09a49ba06124032598d3ad362
Just looks like FreeBSD trips it up far more often, as I've only seen it there.
--J
next prev parent reply other threads:[~2016-04-25 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 17:06 [gentoo-portage-dev] dead emerge processes and/or lockfiles Brian Dolbec
2016-01-17 20:01 ` Zac Medico
2016-01-18 12:37 ` Joshua Kinard
2016-04-24 23:50 ` Joshua Kinard
2016-04-25 0:09 ` Zac Medico
2016-04-25 0:21 ` Joshua Kinard [this message]
2016-04-25 0:36 ` Joshua Kinard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=571D6304.1080004@gentoo.org \
--to=kumba@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox