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 6C9541384B4 for ; Tue, 24 Nov 2015 22:39:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D47A421C0F4; Tue, 24 Nov 2015 22:39:08 +0000 (UTC) Received: from acheron.yagibdah.de (acheron.yagibdah.de [185.55.75.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AA7E621C0EA for ; Tue, 24 Nov 2015 22:39:07 +0000 (UTC) Received: from br-dmz-ip.yagibdah.de ([192.168.1.1] helo=heimdali.yagibdah.de) by acheron.yagibdah.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.85) (envelope-from ) id 1a1MEq-00022f-Ik for gentoo-user@lists.gentoo.org; Tue, 24 Nov 2015 23:39:04 +0100 Received: from lee by heimdali.yagibdah.de with local (Exim 4.85) (envelope-from ) id 1a1MEq-0006GY-Gy for gentoo-user@lists.gentoo.org; Tue, 24 Nov 2015 23:39:04 +0100 From: lee To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] emerging squid indefinitely In-Reply-To: <5653931A.3000701@gmail.com> (Alan McKinnon's message of "Tue, 24 Nov 2015 00:28:42 +0200") Date: Tue, 24 Nov 2015 23:39:01 +0100 Organization: my virtual residence Message-ID: <87ziy3c9a2.fsf@heimdali.yagibdah.de> References: <87oaekg3nz.fsf@heimdali.yagibdah.de> <56532FE3.1060708@gmail.com> <87d1v0e8be.fsf@heimdali.yagibdah.de> <5653931A.3000701@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) Mail-Followup-To: gentoo-user@lists.gentoo.org Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain X-Archives-Salt: e4a6c2b0-54d2-4cf6-88b8-13e0a4775211 X-Archives-Hash: d3c9d2a6a2ee43d94f176eae409369b6 Alan McKinnon writes: > On 23/11/2015 23:04, lee wrote: >> Alan McKinnon writes: >> >>> On 23/11/2015 17:02, lee wrote: >>>> >>>> Hi, >>>> >>>> emerging squid doesn't seem to ever finish: >>>> >>>> >>>> [...] >>>>>>> Emerging (9 of 9) net-proxy/squid-3.5.6::gentoo >>>>>>> Jobs: 8 of 9 complete, 1 running Load avg: 0.37, 0.61, 0.53 >>>> >>>> >>>> What would I look at, without interrupting emerge, to find out what's >>>> going on? >>>> >>> >>> >>> tail the build log >> >> Which is where? There isn't anything in >> /var/log/portage/elog/summary.log, and /var/log/emerge.log only says: >> >> >> 1448288177: ::: completed emerge (8 of 9) net-libs/gnutls-3.3.17.1 to / >> 1448288177: >>> emerge (9 of 9) net-proxy/squid-3.5.6 to / >> 1448288177: === (9 of 9) Cleaning (net-proxy/squid-3.5.6::/usr/portage/net-proxy/squid/squid-3.5.6.ebuild) >> 1448288177: === (9 of 9) Compiling/Merging (net-proxy/squid-3.5.6::/usr/portage/net-proxy/squid/squid-3.5.6.ebuild) >> >> >> It's still pretending that it's compiling, hours later ... >> > > > the build logs are the same place they have always been, in > /var/tmp/portage/..... > > that location is a symlink to: > > /var/log/portage/:-:.log > > and that info is dumped to the console in volume every time emerge fails > for any reason. > > /var/log/portage/elog/summary.log and /var/log/emerge.log are emerge's > logs and contains logs of what emerge is doing. You want build logs to > find out what make and gcc etc are doing. Cool, let's see what it does (It's still emerging.): ,---- | dawn ~ # cat /var/tmp/portage/net-proxy/squid-3.5.6/temp/build.log | * Package: net-proxy/squid-3.5.6 | * Repository: gentoo | * Maintainer: eras@gentoo.org | * USE: abi_x86_64 amd64 caps elibc_glibc htcp ipv6 kernel_linux pam ssl userland_GNU wccp wccpv2 | * FEATURES: preserve-libs sandbox userpriv usersandbox | * Adding group 'squid' to your system ... | * - Groupid: next available `---- ,---- | dawn ~ # ps xa | grep gro | 10563 pts/0 T 0:00 groupadd -r squid | 11315 pts/0 S+ 0:00 grep --colour=auto gro | dawn ~ # `---- It shouldn't take /that/ long to add a group, not even for a system group. ,---- | dawn ~ # grep squid /etc/group | squid:x:245: | dawn ~ # `---- So the group has already been created. Let's create a test group: ,---- | dawn ~ # time groupadd -r test | groupadd: cannot lock /etc/group; try again later. | | real 0m15.003s | user 0m0.000s | sys 0m0.000s | dawn ~ # grep test /etc/group | dawn ~ # ls -la /etc/group* | -rw-r--r-- 1 root root 552 Nov 23 15:16 /etc/group | -rw------- 1 root root 539 Nov 8 19:23 /etc/group- | -rw------- 1 root root 6 Nov 23 15:16 /etc/group.lock | dawn ~ # `---- Well, ok, the file is still locked. 'group-' looks like a backup, and 'group.lock' contains 10563, which is the pid of groupadd. I'd think that's ok. So what all does it take to create a system group? I suppose I could kill groupadd and the emerging might go on, though I wonder what the problem might be and if something else besides making an entry to /etc/group needs to be done. What might require an indefinite delay here? Any ideas?