From owner-freebsd-questions@freebsd.org Sat Oct 20 20:37:15 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D107EFF4DB2 for ; Sat, 20 Oct 2018 20:37:15 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 597EE86DE9 for ; Sat, 20 Oct 2018 20:37:15 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io1-xd29.google.com with SMTP id l25-v6so24941661ioj.0 for ; Sat, 20 Oct 2018 13:37:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=ZLdFRBQYBkj2yxGnc25X1fNUuIXgzG8AjYfY3plhXI8=; b=CzjEKlbfWNJRQ99r8rTmeER58ot7gb/tEJlXF8jpjD1Hs1RFXOSfyLaiBg9YcENa8T yl5VDh18ubQLUj7A2ziAVV+l/dsQHCXNSp8LfZ0w3xdGqvJtdrFnQYEX3F1noxsEWSRx Nwfkl8fX7j8a93OzibLksm5wCGB25Xzdkl5CLl3OXq1/baKSnnzglWKz8fFd8whblRUm ahTiAUHHnzBmgRzfrNa9kMUURQdh0CNfuel+OJk8GZFJqijT5E5AcmLFhBeT4DQ5HegZ yas77GqRcbcTN6/z/+7ImXyNapjJtCPJmwdp6w+Uhwd+kaX4SyjmwlonFWqncGLHBGkv F7gw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=ZLdFRBQYBkj2yxGnc25X1fNUuIXgzG8AjYfY3plhXI8=; b=SqLsO9qmcCVwZkQ4R4r9cy5sFSvAT2QcCUKRAchzEHdf3X5EfnxS4uPqQndra0p1Go DdeqmaOI534z2qZCgiAXSAh17ONbhcQ4zAKBLAPewovYHTyXGuok0epMAfjbCoWraEQ4 4C7z5oZ4UruLezXtuvwAZ/7Usv9MRZ2r4OVRwQzQiujL1WOOPCmqpd9C/VXe20M8nGXl fMqSmViz63YpqDqeYMBgM/ZNjOIIMYd2eCCIc1+gBSpm+LiOVqIDdk+Uvekjln/R+ZoF xghZNlU8XyEKzM11dxxuS+9pXzhj5rfax6eA9+twQfp/wxkX+jDUh2E/eo7Il/ekhrfw vf8A== X-Gm-Message-State: AGRZ1gLOlzIbRphtDFMOiJ47c17VMtqnmxt1QDpojdj6HnjOTIDzcDjR yMThHAAVTQjdBhGQEQLXz7scIQqb X-Google-Smtp-Source: AJdET5eNxyXfnd4GJ9fnGIAjXdl1ZU/IbPyOOovflEsXFZjHavif8rgVm5y1RjyLPiA16CLxrgiU6A== X-Received: by 2002:a6b:5104:: with SMTP id f4-v6mr5339810iob.114.1540067834391; Sat, 20 Oct 2018 13:37:14 -0700 (PDT) Received: from [10.0.10.7] (cpe-65-25-48-31.neo.res.rr.com. [65.25.48.31]) by smtp.googlemail.com with ESMTPSA id c12-v6sm8630371ioq.81.2018.10.20.13.37.12 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 20 Oct 2018 13:37:13 -0700 (PDT) Message-ID: <5BCB91F9.4050607@gmail.com> Date: Sat, 20 Oct 2018 16:37:13 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Erwan David CC: freebsd-questions@freebsd.org Subject: Re: Upgrading ezjail jails from 11.1 to 11.2 References: <5BCB75AC.7090803@gmail.com> <9804d870-e4d1-401f-7b5c-b2d41fe78214@rail.eu.org> In-Reply-To: <9804d870-e4d1-401f-7b5c-b2d41fe78214@rail.eu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Oct 2018 20:37:16 -0000 Erwan David wrote: > Le 10/20/18 à 20:36, Ernie Luzar a écrit : >> Erwan David wrote: >>> Hi, >>> >>> I just upgraded my host system from 11.1 to 11.2 rebooted it (following >>> https://www.freebsd.org/doc/handbook/jails-ezjail.html) then issued the >>> command ezjail-admin update -U -s 11.1-RELEASE >>> >>> However I get a continuous >>> >>> Run '/usr/sbin/freebsd-update fetch' first. >>> No updates are available to install. >>> >>> What should I do to upgrade my jails ? >>> >>> >> Check the questions archives. This was answered in the last few weeks >> or so. >> > Alas the only messages I found are those of > https://docs.freebsd.org/cgi/getmsg.cgi?fetch=80205+0+/usr/local/www/mailindex/archive/2018/freebsd-questions/20180708.freebsd-questions > > Which does not help. I also get posts from the "current" list. Maybe it was there I saw it. Anyhow now I am recalling from memory what the fix was about. This may help point you in the correct direction. As I recall this problem dealt with the directory location of where ezjail processes the update command. The fix was a patch to the source of the ezjail script. The patch source was included in the body of the post. It also said there was a PR about it but the poster could not find it. He had only read the PR titles and nothing about this problem popped out at him. The PR titles may be misleading so all open ezjail PRs may have to be read. If you find yourself between a rock and a hard place I suggest you try qjail. It's a fork of ezjail and uses the new jail.conf nethod of defining jails instead of the old outdated rc.conf method used by ezjail. Moving to qjail will eliminate those warning messages for every jail ezjail starts.