Page 1 of 1

Updating of a jail, using TheBrig, failing

Posted: 27 Dec 2014 15:30
by Ganimed
Hi all,

I've updated in the webinterface of TheBrig (Extensions|TheBrig|FreeBSD Update) all jails. This was successful until to one jail, the ownCloud-jail. Since I've tried to update this jail via the webinterface several times without any success, I decided this to do this manually in the jail by using the terminal.
root@ownCloud:/ # freebsd-update fetch install
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 9.2-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

The following files are affected by updates, but no changes have
been downloaded because the files have been modified locally:
/etc/pkg/FreeBSD.conf

The following files will be added as part of updating to 9.2-RELEASE-p17:
/usr/src/contrib/bind9/lib/isc/counter.c
/usr/src/contrib/bind9/lib/isc/include/isc/counter.h
/usr/src/contrib/tzdata/leap-seconds.list
/usr/src/contrib/tzdata/zone1970.tab
Installing updates...mtree: line 3: no parent node
install: ///usr/src/contrib/bind9/lib/isc/counter.c: No such file or directory
install: ///usr/src/contrib/bind9/lib/isc/include/isc/counter.h: No such file or directory
install: ///usr/src/contrib/tzdata/leap-seconds.list: No such file or directory
install: ///usr/src/contrib/tzdata/zone1970.tab: No such file or directory

done.
It seems like that there is a problem with mtree (see colored lines above). Furthermore, the listed files cannot installed since the paths are not existing. Does somebody know how to solve this problem? Or how is it possible to force updating? Is there a way to override this?

Thank's in advance.

NAS4Free 9.2.0.1 (revision 972) x86-full
VX800 AWRDACPI VIA C7-D Processor 1500MHz 1983MiB RAM

VIA VT6202 USB 2.0 controller VIA 83C572 USB controller IP1001
10/100/1000 media interface

Re: Updating of a jail, using TheBrig, failing

Posted: 27 Dec 2014 19:30
by Ganimed
Or in other words how is it possible to force the update action from 9.2-RELEASE-p11 to 9.2-RELEASE-p17?

I've tried the update action for the ownCloud-jail via the webinterface (Extensions|TheBrig|FreeBSD Update) by marking the jail and clicking the fetch- and afterwards the install-button. But this changed nothing. Also the updating of the portstree in Extensions|TheBrig|Central Ports did not made any change. Executing the command freebsd-update fetch install in the jail does also not work.
What also strange is, I remember me when I created the jail for some month ago, that I have set the jail type to "full". But now for unknown reasons the jail type in TheBrig|Jail|Edit is set to slim. If this don't affect my system in the jail, I will ignore it. But maybe it is a possible reason why I can't update the jail.

Has someone an idea what I can also try?

Re: Updating of a jail, using TheBrig, failing

Posted: 28 Dec 2014 22:41
by Ganimed
Problem solved ... :D

After trying several different approaches, I've found out where the error was. It was quite simple to repair it afterwards.
The error was in the conf.xml file under /conf. I guess some time ago in the past, the saving of some changes in the webinterface were incorrect. Either in "Extensions|TheBrig" or somewhere else in the webinterface is a small bug for writing back the changes in conf.xml.
The error was that in in the config file was written <jail_type/> and not <jail_type>full</jail_type> instead. Hence the interface selected automatically the 'slim' type and the update process failed every time when the install-button was pressed in "Extensions|TheBrig|FreeBSD Update".
After correcting the bug in the config file with an editor, the update process for the jail worked correctly.

Maybe it is a good idea to check the write-methods for saving or updating the conf.xml file.

Re: Updating of a jail, using TheBrig, failing

Posted: 27 Jan 2015 07:32
by fsbruva
Ganimed - it is an excellent idea.

The version of TheBrig that most people use has numerous bugs - it was called "testing" branch for a reason!! This (along with several other bugfixes) will be fixed in the next major release of TheBrig.