From owner-freebsd-stable@freebsd.org Wed Oct 26 08:56:38 2016 Return-Path: Delivered-To: freebsd-stable@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 7F17AC22B2E for ; Wed, 26 Oct 2016 08:56:38 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EAC58630; Wed, 26 Oct 2016 08:56:37 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id u9Q8uX5G011047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 26 Oct 2016 10:56:34 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: matthew@FreeBSD.org Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id u9Q8uP7j065526; Wed, 26 Oct 2016 15:56:25 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: Dying jail To: Matthew Seaman , freebsd-stable@freebsd.org References: <581064BB.1030500@rdtc.ru> <591438f4-7ae3-252a-c604-8491787ad9f0@freebsd.org> From: Eugene Grosbein Message-ID: <58106FB9.6050307@grosbein.net> Date: Wed, 26 Oct 2016 15:56:25 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <591438f4-7ae3-252a-c604-8491787ad9f0@freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=3.0 required=5.0 tests=BAYES_00, DATE_IN_FUTURE_96_Q, LOCAL_FROM autolearn=no version=3.3.2 X-Spam-Report: * 2.7 DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-Spam-Level: ** X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2016 08:56:38 -0000 On 26.10.2016 15:45, Matthew Seaman wrote: > On 10/26/16 09:09, Eugene Grosbein wrote: >> Recently I've upgraded one of my server running 9.3-STABLE with jail containing 4.11-STABLE system. >> The host was source-upgraded upto 10.3-STABLE first and next to 11.0-STABLE >> and jail configuration migrated to /etc/jail.conf. The jail kept intact. >> >> "service jail start" started the jail successfully >> but "service jail restart" fails due to jail being stuck in "dying" state for long time: >> "jls" shows no running jails and "jls -d" shows the dying jail. >> >> How do I know why is it stuck and how to forcebly kill it without reboot of the host? > > I've seen this fairly frequently. I think it may have something to do > with old network connections waiting to be cleaned up -- if you run > sockstat it's all the stuff that gets listed at the end with lots of > question marks. BICBW. My jails has public IPv4 distinct from host's one and sockstat shows no lines for jail's IP. > One tip I've found is *not* to specify the JID number in jail.conf, and > just let the system allocate a new one as it feels necessary. If you've > scripting that uses the JID to operate on a specific jail, it's easy to > substitute the jail name instead. I do not specify JID number in jail.conf. OTOH, its jail configuration section in jail.conf is numeric-named and the same number automatically assigned as its jid for unknown reason.