Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Oct 2018 16:37:13 -0400
From:      Ernie Luzar <luzar722@gmail.com>
To:        Erwan David <erwan@rail.eu.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Upgrading ezjail jails from 11.1 to 11.2
Message-ID:  <5BCB91F9.4050607@gmail.com>
In-Reply-To: <9804d870-e4d1-401f-7b5c-b2d41fe78214@rail.eu.org>
References:  <ff62ad4a-d77e-9adb-3baf-ff39fd9651f7@rail.eu.org> <5BCB75AC.7090803@gmail.com> <9804d870-e4d1-401f-7b5c-b2d41fe78214@rail.eu.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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.







Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?5BCB91F9.4050607>