From owner-freebsd-pkg@freebsd.org Sun Apr 10 10:24:44 2016 Return-Path: Delivered-To: freebsd-pkg@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF4F5B090F2 for ; Sun, 10 Apr 2016 10:24:44 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 452581299 for ; Sun, 10 Apr 2016 10:24:43 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id u3AAOR4Q084353; Sun, 10 Apr 2016 13:24:27 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Sun, 10 Apr 2016 13:24:27 +0300 (MSK) From: Dmitry Morozovsky To: Michael Grimm cc: freebsd-pkg@freebsd.org Subject: Re: lock problem with contemporary poudriere-devel In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Sun, 10 Apr 2016 13:24:28 +0300 (MSK) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2016 10:24:44 -0000 On Sun, 10 Apr 2016, Michael Grimm wrote: > Dmitry Morozovsky wrote: > > > after some unspecified set of things[tm] I now have problems with one of the > > poudriere sets: consistent > > > > ====>> Warning: Failed to acquire update_stats lock > > > > ckearing /tmp content does not help; defensive reboot does not either. > > > > I tried to track this via source, but failed. Packages seem to be built well, > > only post-processing are locked. > > > > Any hints? Thanks! > > Sorry, no hints. But I am seeing the same with poudriere bulk builds (poudriere-devel-3.1.99.20160216). > > After running a bulk build of 280 ports by ? > > poudriere bulk -f /usr/local/etc/poudriere.d/pkglist -j stable -J 20 -c > > ? poudriere will hang after having successfully built all 280 ports with: > > mike> ps -Af | egrep '(locked_mkdir|poudriere)' > 728 1 SN 0:00.00 locked_mkdir 30 /tmp/.poudriere-lock-62843-stable-default-update_stats > 62843 1 IN 0:02.24 sh -e /usr/local/share/poudriere/bulk.sh -f /usr/local/etc/poudriere.d/pkglist -j stable -J 20 -c > 62997 1 SN 0:06.41 sh -e /usr/local/share/poudriere/bulk.sh -f /usr/local/etc/poudriere.d/pkglist -j stable -J 20 -c > 63002 1 IN 0:00.82 sh -e /usr/local/share/poudriere/bulk.sh -f /usr/local/etc/poudriere.d/pkglist -j stable -J 20 -c > > I have to kill all bulk.sh in order to stop the poudriere run. All ports have been build correctly, though. Yes, exactly the same. What puzzles me most is that there are 4 jails and one package set. In my case, building script does apply "poudriere bulk -z server -j %1 -f ${HOME}/poudriere/poudriere-server-list" {10,9}{amd64,i386} -- and only with 10amd64 jail it has such lock. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------