From owner-freebsd-ports@FreeBSD.ORG Sat Aug 11 09:21:21 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id 10F13106564A for ; Sat, 11 Aug 2012 09:21:20 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 8B60B14F39A; Sat, 11 Aug 2012 09:21:10 +0000 (UTC) Message-ID: <50262406.2000302@FreeBSD.org> Date: Sat, 11 Aug 2012 02:21:10 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Michael Ranner References: <50250E97.4000004@ranner.eu> <502523D4.4050200@ranner.eu> <50258D15.8010606@FreeBSD.org> <5025B03A.5080707@FreeBSD.org> <50261211.3090502@ranner.eu> <5026133B.5000500@FreeBSD.org> <502616A8.5010200@ranner.eu> In-Reply-To: <502616A8.5010200@ranner.eu> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, HU Dong Subject: Re: portmaster 3.13.13 real endless loop "Waiting on fetch & checksum..." X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Aug 2012 09:21:21 -0000 On 08/11/2012 01:24 AM, Michael Ranner wrote: > As I already told, "portmaster -F" is fetching to /usr/ports/distfiles > and appending to fetchlog in /tmp In your other message you indicate that the fetchlog in /tmp is empty. So I'm confused. > But "portmaster -i" does this not! By the time it gets to the 'make checksum' process there is nothing different about the code for -F or -i. Based on what you're describing it sounds like your fetch process is hanging, and/or not exiting properly. What portmaster does is launch a subshell in the background that has a mini-script to run 'make checksum'. That target will verify the files if they exist, or fetch them and then verify if they do not. Once that is done, the mini-script removes the fetchlog which acts as a sort of flag to signal portmaster that it's done. If the fetch part of the process is completing, but the actual 'make checksum' target is not, that's an OS or ports infrastructure bug. If the fetch is not completing it could be an OS bug, or it could be a stalled/slow remote site, a bad Internet connection, or any of a half-dozen other things. Either way, I seriously doubt the code in portmaster is at fault. That code hasn't changed in many years. The only other thing I can think of to try is to start a build for one of the ports you're having trouble with (after removing the distfiles of course) and just let it run. While it's running, check these things: 1. Does the distfile actually get downloaded? 2. Does the fetch complete? That is, does the full file get downloaded, which matches the size and checksum in the distinfo file? 3. If the fetching of the file completes, does 'ps axww' show that a fetch process for that file is still underway? 4. If the fetching of the file completes, can you run 'make checksum' in the port directory and get a positive result? 5. What happens if you just let the portmaster process run for a few hours? Doug