Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 9 Oct 2007 10:16:15 -0400
From:      Bill Moran <wmoran@collaborativefusion.com>
To:        freebsd-jail@freebsd.org
Cc:        netops@collaborativefusion.com
Subject:   Mysterious jail lockups
Message-ID:  <20071009101615.bd2601de.wmoran@collaborativefusion.com>

next in thread | raw e-mail | index | archive | help

Has anyone else seen this?

The symptoms are a jail that has no processes in it, and thus can not
be stopped/killed/whatever.  Only solution is to reboot the host system.
Trying to jexec into the jail results in an error, so new processes can't
be started therein.

It doesn't happen very often, and I've been unable to reproduce it on
demand.  What I'm looking for at this point are whether or not anyone
else has seen this, and advice on how to track it down/reproduce it, with
the eventual goal of fixing the problem.

It would be nice if there were a command, let's say "jkill" that killed
the _jail_.  There is a port called jkill that (allegedly) does this, but
looking at the perl code, all it does it loop through a ps listing
killing off processes.  In the event of a jail with no processes, this
doesn't help any.

Theoretically, this would be some sort of kernel bug, whereby the
reference counter to the jail is not properly decremented when processes
die and thus the jail never shuts down.  Given the infrequency of the
occurrence and my inability to produce a reproducible case, I expect
it to be challenging to track down.

Any advice?

-- 
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran@collaborativefusion.com
Phone: 412-422-3463x4023



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071009101615.bd2601de.wmoran>