From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 50FA9138206 for ; Mon, 25 Apr 2016 00:09:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DE18721C040; Mon, 25 Apr 2016 00:09:51 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4E3A421C03E for ; Mon, 25 Apr 2016 00:09:51 +0000 (UTC) Received: from [192.168.0.20] (ip68-5-185-102.oc.oc.cox.net [68.5.185.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 47B6D34092D for ; Mon, 25 Apr 2016 00:09:50 +0000 (UTC) Subject: Re: [gentoo-portage-dev] dead emerge processes and/or lockfiles To: gentoo-portage-dev@lists.gentoo.org References: <20160117090635.6b77890d.dolsen@gentoo.org> <569BF303.3060408@gentoo.org> <569CDC87.9000902@gentoo.org> <571D5BCE.6070304@gentoo.org> From: Zac Medico Message-ID: <571D604C.9020704@gentoo.org> Date: Sun, 24 Apr 2016 17:09:48 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <571D5BCE.6070304@gentoo.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Archives-Salt: 44465f50-5876-43a0-a9f6-f0b7a0524c6d X-Archives-Hash: a6f046b24ece29c6792963c111a33266 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. -- Thanks, Zac