Dying jail

Eugene Grosbein eugen at grosbein.net
Wed Oct 26 08:56:38 UTC 2016


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.




More information about the freebsd-stable mailing list