From owner-freebsd-jail@freebsd.org Sat Oct 28 23:16:53 2017 Return-Path: Delivered-To: freebsd-jail@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 012C5E500BB for ; Sat, 28 Oct 2017 23:16:53 +0000 (UTC) (envelope-from freebsd@posteo.co) Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A615E8389F for ; Sat, 28 Oct 2017 23:16:52 +0000 (UTC) (envelope-from freebsd@posteo.co) Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 46EC520BCE for ; Sun, 29 Oct 2017 01:15:23 +0200 (CEST) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3yPc6K6KSMzyxS; Sun, 29 Oct 2017 01:15:21 +0200 (CEST) MIME-Version: 1.0 Date: Sun, 29 Oct 2017 10:15:21 +1100 From: Rami To: freebsd-jail@freebsd.org Subject: Updating jails base binaries Reply-To: freebsd@posteo.co Mail-Reply-To: freebsd@posteo.co Message-ID: <515c9089dfd25ba38df586f1274ff97f@posteo.net> X-Sender: freebsd@posteo.co User-Agent: Posteo Webmail Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2017 23:16:53 -0000 Hi everyone, I have an issue which I got aware of by accident couple of days ago while I was upgrading a port in the jail. I have a jail created using ezjail and running Gitea port in it. Recently Gitea got updated so after upgrading the installed port in the jail, the service started complaining as below _~ # SERVICE GITEA START _ daemon: illegal option -- S usage: daemon [-cfr] [-p child_pidfile] [-P supervisor_pidfile] [-t title] [-u user] command arguments ... After a bit of investigating we figured out that the binaries in the jail are behind the host (and the jail kernel release). please check below The jail where the gitea is running # freebsd-version 11.1-RELEASE-p2# uname -a #uname -a FreeBSD git.jail 11.1-RELEASE-p1 FreeBSD 11.1-RELEASE-p1 #0: Wed Aug 9 11:55:48 UTC 2017 _ROOT@AMD64-BUILDER.DAEMONOLOGY.NET_:/usr/obj/usr/src/sys/GENERIC amd64 # sha256 /usr/sbin/daemon SHA256 (/usr/sbin/daemon) = 2f1d9b434cae89c67aefa9798b87fd97bcde2f70b2ba0140b7052ae6536aaf8a # /USR/SBIN/DAEMON _USAGE: DAEMON [-CFR] [-P CHILD_PIDFILE] [-P SUPERVISOR_PIDFILE]_ [-T TITLE] [-U USER] COMMAND ARGUMENTS ... The host ~ % freebsd-version 11.1-RELEASE-p2~ % UNAME -A _FREEBSD SERVER-LINODE-1-GIT 11.1-RELEASE-P1 FREEBSD 11.1-RELEASE-P1 #0: WED AUG 9 11:55:48 UTC 2017 __ROOT@AMD64-BUILDER.DAEMONOLOGY.NET__:/USR/OBJ/USR/SRC/SYS/GENERIC AMD64_~ % sha256 /usr/sbin/daemon SHA256 (/usr/sbin/daemon) = 2b029a5c274c6292870caf35470041c2553b768346bb001c97d447877bc9caf5~ % /USR/SBIN/DAEMON _USAGE: DAEMON [-CFRS] [-P CHILD_PIDFILE] [-P SUPERVISOR_PIDFILE]__ [-U USER] [-O OUTPUT_FILE] [-T TITLE]__ [-L SYSLOG_FACILITY] [-S SYSLOG_PRIORITY]_ [-T SYSLOG_TAG] [-M OUTPUT_MASK] _COMMAND ARGUMENTS ..._ I will always update the jails using # EZJAIL-ADMIN UPDATE -U and the ports _# EZJAIL-ADMIN UPDATE -P_ so it seems the kernel been updated yet not the binaries.... can anyone please advise me to what is the best way to keep the whole system kernel, base, and ports up to date in the jail (and keep the base binaries and kernel match the same release) Thanks so much Rami