From owner-freebsd-jail@FreeBSD.ORG Tue Sep 11 22:14:38 2012 Return-Path: Delivered-To: freebsd-jail@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A8D2D106567D for ; Tue, 11 Sep 2012 22:14:38 +0000 (UTC) (envelope-from jamie@FreeBSD.org) Received: from m2.gritton.org (gritton.org [199.192.164.235]) by mx1.freebsd.org (Postfix) with ESMTP id 750438FC25 for ; Tue, 11 Sep 2012 22:14:37 +0000 (UTC) Received: from guppy.corp.verio.net (fw.oremut02.us.wh.verio.net [198.65.168.24]) (authenticated bits=0) by m2.gritton.org (8.14.5/8.14.5) with ESMTP id q8BMEUTc042428; Tue, 11 Sep 2012 16:14:31 -0600 (MDT) (envelope-from jamie@FreeBSD.org) Message-ID: <504FB7C1.9010103@FreeBSD.org> Date: Tue, 11 Sep 2012 16:14:25 -0600 From: Jamie Gritton User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120126 Thunderbird/9.0 MIME-Version: 1.0 To: Jack Stone References: <504B8B31.6030202@sage-american.com> In-Reply-To: <504B8B31.6030202@sage-american.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-jail@FreeBSD.org Subject: Re: Upgrading FBSD-7.0 --> 7.4 and Jail won't start X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 22:14:38 -0000 On 09/08/12 12:15, Jack Stone wrote: > uname -a > FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD 7.0-RELEASE-p9 #2: Sun > Jan 18 19:59:27 CST 2009 root@mail.sagedata.net:/usr/obj/usr/src/sys/SMP > i386 > > Have been running and upgrading host+jail for years and through several > versions of FreeBSD. However, I got behind on updates and now playing > catchup on an important production server. > > Tried to upgrade fbsd-7.0 --> 7.4 followed by upgarde of a jail as in > past. However, on reboot, the host booted up OK, but the jail would not > work. On re-trying to start the jail, only got a crytic error about > missing syscalls. I've never seen this before and don't have a clue what > needs fixing. > > My setups for starting jails are in the /etc/rc.conf file and such still > works here in Texas on local servers when upgraded. However, the > production server is in Los Angeles and cannot react to any serious boot > problems without sending the ISP owner downtown to switch my HD back to > a bootable clone before the upgrade attempts. I cannot afford to have > the jail offline as it contains my SSL stuff vital to the business. > > I manage the jails using the tools that came with Jail(8). > > Can anyone point me in the right direction on this issue? Do I now need > stuff in sysctl.conf for the jail? Or.....???? > > Thanks for any help!! Your mention of sysctl.conf makes me wonder: missing syscalls, or missing sysctls? There was a change between 7.0 and 7.4 where some jail-related sysctls were added. There was also a change to the jail(2) system call, with a new version of struct jail - but the old version continues to work. I don't think there were and new syscalls at that point - perhaps other new sysctls? Is the problem in actually creating the jail, or in processes that run inside the jail? If the latter, there's really a lot of things that could be the problem, if you're running an un-updated user space. Not that they *should* happen, mind you, but still a lot more room for something to go wrong. - Jamie