From owner-freebsd-questions@freebsd.org Sun Sep 4 11:48:22 2016 Return-Path: Delivered-To: freebsd-questions@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 107DAA9DEB5 for ; Sun, 4 Sep 2016 11:48:22 +0000 (UTC) (envelope-from wout@canodus.be) Received: from mail1.canodus2.canodus.be (mail1.canodus2.canodus.be [83.149.89.38]) by mx1.freebsd.org (Postfix) with ESMTP id D0ADBC01 for ; Sun, 4 Sep 2016 11:48:21 +0000 (UTC) (envelope-from wout@canodus.be) Received: by mail1.canodus2.canodus.be (Postfix, from userid 65534) id 7BC93336451; Sun, 4 Sep 2016 13:41:28 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail1.canodus2.canodus.be X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Received: from t440s (d8D877BCE.access.telenet.be [141.135.123.206]) by mail1.canodus2.canodus.be (Postfix) with ESMTPSA id 389AA336438; Sun, 4 Sep 2016 13:41:28 +0200 (CEST) Message-ID: <1472989287.1637.9.camel@canodus.be> Subject: Re: Jail not starting at Boot From: Wout =?ISO-8859-1?Q?Decr=E9?= To: freebsd-questions@freebsd.org Cc: ricky1252@hotmail.com Date: Sun, 04 Sep 2016 13:41:27 +0200 In-Reply-To: Organization: Canodus Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.9-1+b1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Sep 2016 11:48:22 -0000 Hi I had a similar problem, not all jails started at boot. After a lot of rebooting I found a solution. I use exec.prestart to nullfs mount /usr/ports to {jail}/usr/ports like so: exec.prestart = "/sbin/mount -t nullfs -o ro /usr/ports /usr/jails/$name/usr/ports"; The jail init script will not start a jail if this exec.prestart command fails. After adding nullfs_load="YES" to /boot/loader.conf (so the module is loaded early in boot), no more problems. Hope this will help you too. Best regards Wout