XigmaNAS

Posted: **26 Jun 2014 22:29**

Problem: The Extensions-Menu in the WebGUI doesn't survive a reboot.

I'm running an embedded 64-bit N4F-972 install from USB stick with data on a ZFS mount.

-----------------------------------------------------------------------------------------------------------------------------
BOTH PROBLEMS SOLVED - see bottom of post for details
-----------------------------------------------------------------------------------------------------------------------------

When I install TheBrig as outlined in the 3-step process of the original post (as root over ssh), this worked almost fine.

I did get the following warning from the install script:

Code: Select all

Warning: file(/var/tmp/temporary/conf/ext/thebrig/lang.inc): failed to open stream: No such file or directory in /mnt/pool-1/ds-1/ds-jails/temporary/conf/bin/change_ver.php on line 6
No need updates 
You use fresh version
rmdir: temporary: No such file or directory

From looking at change_ver.php I guessed that shouldn't have been too bad because lang.inc is only needed to determine a previously installed version, so I went on. The install did go through, after all. After refreshing the WebGUI I completed (I think) the rudimentary config, downloaded base and 32bit-tarballs and created a jail.

But after a reboot the WebGUI doesn't show the Extensions menu any more.

I retried the installation and got following output:

Code: Select all

(... more lines...)
x conf/sbin/
x conf/sbin/freebsd-update
x conf/sbin/portsnap
x thebrig_install.sh

Warning: file(/var/tmp/temporary/conf/ext/thebrig/lang.inc): failed to open stream: No such file or directory in /mnt/pool-1/ds-1/ds-jails/temporary/conf/bin/change_ver.php on line 6
You use old thebrig version, we reinstall it 
Renaming 64 bit ftp binary
Congratulations! Thebrig updated . Navigate to rudimentary config tab and push Save 
rmdir: temporary: No such file or directory

Something must be messed up with some path or something because lang.inc still isn't found and the rmdir also fails.
This time the WebGUI didn't even offer the rudimentary configuration (hinting that the previous installation hadn't been removed cleanly?).
And again, after a reboot the WebGUI lost the Extensions entry.

As a third try, I deleted everything in my ds-jails dataset and reinstalled. The install went through with the same warnings but this time I don't get the Extensions menu at all, not even before reboot.
I suppose deleting everything like that was not a very good idea but I didn't see another way to uninstall (because the WebGUI was unavailable). I noticed traces of TheBrig in config.xml and I'm sure there are more in other places that weren't cleanly uninstalled.

Three questions:
1. Why didn't the install work in the first place? Something with paths/directories/perms?
2. What should I clean up to make everything work, and make TheBrig's WebGUI entry persist over reboots?

Any help would be appreciated - thanks!

-----------------------------------------------------------------------------------------------------------------------------
SOLVED:
The first problem must have had to do with permissions. My ds-jails dataset had no rwx rights for "other".
With those rights theBrig installed fine. I still wonder what the best permissions setting might be (most secure setting that still works). Maybe I can tighten
them back down now installation's finished? Answers still appreciated!

The WebGUI entry not appearing after reboot was funny: theBrig is launched by a postInit-script entry that apparently works only of it's first in the list of entries (I have another script running). When I interchanged the two scripts they both started fine.

Posted: **01 Jul 2014 13:22**

Hi,

how do i delete a stopped jail? I selected it for deletion, and applied the changes, and after this, the web gui becomes inresponsive. However, i can still SSH into the NAS and do stuff. So i waited, maybe the deletion process takes long time. But after one hour i cancelled, that means, i rebooted the NAS because the web sevice was still inresponsive. However, the jail is still there, in the filesystem and in the web gui.

Posted: **01 Jul 2014 14:20**

simonszu wrote:how do i delete a stopped jail? I selected it for deletion, and applied the changes, and after this, the web gui becomes inresponsive.

This is because the deletion process do a backup of your entire jail so you can restore later.

In your case perhaps your jail was to big in size and need a lot of time to do this operatión.

Please revise that your jail are really deleted or , delete it by hand : http://wiki.nas4free.org/doku.php?id=do ... s&s[]=jail

(search for deleting a jail and use apropiate paths )

If you create a test jail and next delete it, you see that is deleted really fast because is really small in size, and appear in the tarball selector like yourjail_backup.tbz or something simmilar.

Posted: **02 Jul 2014 17:02**

This is a continuation of the issue I first posted here: viewtopic.php?p=36356#p36356

So, I have a working install on a 9.1 box that I haven't upgraded or touched since 02/14 (install was a breeze, still works great). I have been attempting to install on a new box running 9.2 and the latest Nas4free. This new box just will not install successfully. I go through all the initial steps, everything installs successfully (or, so it tells me), but I can never start the jail, I keep getting unable to mount & folder/directory does not exist errors. Checking in my Jail folder, it's because the "basejail" and "template" folders are missing.

I thought this might be an issue with FreeBSD 9.2, so I reformatted the embedded USB to the previous Nas4free release using 9.1, wiped my harddrives, and booted/installed from that. Same exact problem with theBrig, can't start the jail & no basejail folder (or template) is present. Everything tells me the install completes successfully, but something is preventing the basejail & template folders from being created.

After two days of trying unsuccessfully to troubleshoot the issue, I decided this morning to wipe everything again and install the latest 9.2 Nas4free release and try theBrig again. Still not working. I did a side by side permissions comparison of my working install & this troubled install's files & folders, everything looks identical. There are several new files in this latest version of theBrig, but otherwise everything looks the same.

At this point, I think the missing basejail is the problem. Is there an easy way to manually create the basejail folder & it's contents? Why it's not created is the larger issue, but I just want to get a working install, at this point.

Posted: **02 Jul 2014 20:55**

knotworking wrote: Is there an easy way to manually create the basejail folder & it's contents?

Let me say I do not know anything specifically about theBrig. However in general, you can unpack "base.txz" from FreeBSD's official distfiles into a jail folder. And the result will be provided most things. Here you can see in Finch the code how to download them all manually. There are some optional ones too. Can take or leave. You definately don't need the files "kernel.txz" and "src.txz" in a jail. They are no use and can be omited. TIP: for copy-paste that code must use 'bash' or 'sh' shell. Not 'csh' or 'tcsh'.

https://github.com/dreamcat4/finch/blob ... bsd#L47-53

knotworking wrote:Why it's not created is the larger issue, but I just want to get a working install, at this point.

Or perhaps if you took my original suggestion previously. (from some 1-2 week ago), and try Finch instead as an alternative. Then by now, you would already know how to use the "qjail" command line tool. It could not be more difficult than what you have gone through already.

Of course, the correct option is to fix theBrig. If you can find in theBrig code where the problem is caused. That is a very good idea also. Sorry not to help in that respect. I undertand FreeBSD jails. However I do not know anything about coding in PHP / web extensions.

Posted: **02 Jul 2014 21:27**

Hi Dreamcat, thanks for the tip.

I did indeed try Finch. I installed it without any trouble, but I could not use qjail, apparently there is an issue with the version of qjail that was installed (3.4) and 9.2. There was a message in the install log that said I needed FreeBSD 9.3 or 10.0 for that version of qjail. I tried to create a new jail anyway (following the how-to here: http://dreamcat4.github.io/finch/jails-how-to/), and I could not get it to create the jail. I'd issue the create command, and I'd get an error message back complaining about no such file or directory.

I figured this was because of the version issue, so I thought I could upgrade the FInch version of FreeBSD to fix the error. I started the process here http://dreamcat4.github.io/finch/upgrading/#toc_7 but then I reread everything and realized I would (apparently) have to upgrade Nas4free's FreeBSD version after I upgraded the Finch version. I gave up there, seemed like a long road ahead of me with potential pitfalls, so that was the point where I decided to just try and downgrade to the previous Nas4free release for 9.1 and try to install theBrig on that (of course, that didn't work).

Sorry I didn't submit a formal report to you on the issue I had with Finch, this is just a home nas build I am doing for a neighbor and I am desperate to just get it done and out of my life. I've lost days trying to get some jail solution working on it....

Posted: **02 Jul 2014 22:17**

knotworking wrote:I did indeed try Finch. I installed it without any trouble, but I could not use qjail, apparently there is an issue with the version of qjail that was installed (3.4) and 9.2. There was a message in the install log that said I needed FreeBSD 9.3 or 10.0 for that version of qjail.

Ok. Well I can certainly help here. Unfortunately the error msg was not written by me. It is a red herring. And updating FreeBSD is not the solution in this time (because NAS4Free host isn't available for 9.3 any time yet).

What happened, the reason for this problem was because the Author of qjail program did some new version check.This issue affect very recently new installs (not the existing users). As then qjail-3.4 is auto-realeased on pgkng repository. When that happen they do not tell me exactly, and then the previous qjail 3.3 package (that worked OK) is immediately removed / unavailable for download anymore.

I have inspected the new coded in qjail 3.4 program already, and not found any different (in terms of FreeBSD 9.2 compatibility) that all the previous versions we already for the last 6 months. So it's nothing to worry about that. Since no new problems in qjail program itself, we just override this check.

Fix was uploaded yesterday. So now finch can auto-patch new version of qjail program (3.4). However you will need to run some commands like this:

Code: Select all

# updating finch will auto-patch qjail-3.4
sudo finch update -y -f
sudo finch chroot

# for populate base jail 'sharedfs' folder
qjail install -f /var/distfiles/finch

# for populate the ports tree in jail 'sharedfs' folder
portsnap fetch update
qjail update -P

# restart qjail
service qjail.bootime restart

I think these steps written above ^^ should work for you because we tried already with another person yesterday (Simon). Who had same problem. He said it work OK afterwards. If any further problem please let me know and I will try to help again.

Posted: **02 Jul 2014 22:32**

Good to know, if I can't get theBrig working this time, I think I'll have to give Finch another go.

I tried again to install from scratch, following the two tips from Alexey he left a month of so ago (downloading the setup to the root folder). Same issue as before, jail won't start and basejail was missing. I downloaded & decompressed the base.txz 9.2 to the basejail folder, that log error message went away, only to be followed by errors about missing folders (basejail, proc, log) in my plex jail. Manually created them, and now it won't do anything. Jail won't start and nothing is logged. I'm completely baffled :/

FYI: I had only been trying to create slim jails up to this point. I just deleted the slim jail and tried to add a full jail, same issues as the slim jail.

Posted: **03 Jul 2014 16:56**

So I decided to add a new jail to my working install (I've had Plex running on it since January with no problems), I didn't want to mess with my working Plex jail, but I was hoping creating a new jail on my working boc would maybe give me some fresh clues to what was happening on my problem box. Lo & behold, I create the new jail named "test" and it won't start, either. It's giving me the same errors as the problem box!!

root: /etc/rc.d/jail: WARNING: devfs_domount(): Unable to mount devfs on /mnt/Poolz/Jail/test//dev
root: /etc/rc.d/jail: WARNING: devfs_mount_jail: devfs was not mounted on /mnt/Poolz/Jail/test//dev

I can start & stop the plex jail with no problems at all. I see the double slashes above, but I don't think that's the problem, because this is the same script that mounts the plex jail (right?). Other than the IP address, the test jail has the exact same settings as the plex jail. I've tried it with the plex jail stopped/started, doesn't make any difference.

Posted: **07 Jul 2014 14:53**

Okay, fixed it. Feeling a bit dumb right about now, but reporting the fix in-case someone else finds themselves with the same problem. When I was creating the jails, at the bottom of the configuration page there is "Installation Source." I was leaving the Jail Source as "From Archive" and saving without checking any of the "Official FreeBSD Flavor" checkboxes (I was assuming by selecting the From Archive option, these would automatically be used). I decided to check all the check boxes (FreeBSD-amd64*.base.txz, etc.,), and voila, a working jail....

Posted: **10 Jul 2014 15:45**

Hi,

I have a problem with the jail created using the brig feature.

I created a jail without any major issues - it has rtorrent + rutorrent working on the lighttpd. Apps worked without any problems, until I tested if it still will work after rebooting NAS. Unfortunatelly it doesn't - the jail is stopped and cannot be started. There are no logs either.

I tried to create other vanilla jails, but they are working after reboot. Does anyone know what should I do to fix this problem? My version of the N4F is the newest one: 972.

Posted: **31 Jul 2014 00:04**

Hello,
I tried to follow these three steps to istall thebrig over ssh.
Every Time I try that last command I get following logs.
I have already given Jail/ full rights.
How can I make the install succesful?

Code: Select all

nas4free: ~ # /bin/sh /tmp/thebrig_install.sh /mnt/tank/Jail/
[: -eq: unexpected operator
[: -eq: unexpected operator
Retrieving the most recent version of TheBrig
master.zip                                    100% of  181 kB  397 kBps 00m00s
Unpacking the tarball...
x README
x conf/
x conf/bin/
x conf/bin/ftp_amd64
x conf/bin/ftp_i386
x conf/bin/thebrig_fetch.sh
x conf/bin/thebrig_start.php
x conf/bin/thebrig_start.sh
x conf/bin/thebrig_stop.sh
x conf/ext/
x conf/ext/thebrig/
x conf/ext/thebrig/extensions_thebrig.php
x conf/ext/thebrig/extensions_thebrig_check.php
x conf/ext/thebrig/extensions_thebrig_config.php
x conf/ext/thebrig/extensions_thebrig_download.php
x conf/ext/thebrig/extensions_thebrig_edit.php
x conf/ext/thebrig/extensions_thebrig_tarballs.php
x conf/ext/thebrig/extensions_thebrig_tools.php
x conf/ext/thebrig/functions.inc
x conf/ext/thebrig/lang.inc
x conf/ext/thebrig/menu.inc
x conf/ext/thebrig/off_small.png
x conf/ext/thebrig/on_small.png
x conf/freebsd-update.conf
x conf/periodic.conf
x conf/portsnap.conf
x thebrig_install.sh
No input file specified.
You use fresh version
rmdir: temporary: No such file or directory

Posted: **31 Jul 2014 07:37**

you are trying to install master branch:

Retrieving the most recent version of TheBrig
master.zip 100% of 181 kB 397 kBps 00m00s
Unpacking the tarball...

and need to install working branch:

Code: Select all

/bin/sh /tmp/thebrig_install.sh /mnt/tank/Jail/ 2

notice the 2 at the end.

Posted: **31 Jul 2014 20:13**

Hi
I’ve followed the youtube installation and all seemed fine until i pressed the "yes" button.

Whats the problem to this?

Posted: **31 Jul 2014 20:21**

This seems to be part of the problem
/etc/rc.conf: security.jail.chflags_allowed=1: not found
Ive have it added this way:

Posted: **31 Jul 2014 21:19**

I have removed the variable security.jail.chflags_allowed from rc.conf and adcded it in sysctl.conf. Now when i send "sysctl security.jail" the flag is set to "1". But i still have the same problem when trying to save a new jail. This "Warning: fwrite() expects parameter 1 to be resource, boolean given " seen in the picture abowe.

Posted: **31 Jul 2014 22:51**

try to define inside the jail:

Code: Select all

echo security.jail.chflags_allowed=1 >> /mnt/Data/jail/OwnCloud/etc/rc.conf

/mnt/Data/jail/OwnCloud/etc/rc.conf: security.jail.chflags_allowed=1

Posted: **31 Jul 2014 22:57**

Mizma wrote:I have removed the variable security.jail.chflags_allowed from rc.conf and adcded it in sysctl.conf. Now when i send "sysctl security.jail" the flag is set to "1". But i still have the same problem when trying to save a new jail. This "Warning: fwrite() expects parameter 1 to be resource, boolean given " seen in the picture abowe.

are you totaly sure that install thebrig working branch???, it's like you install thebring master.

your step 3 in this HOWTO viewtopic.php?f=79&t=3894 must be:

Code: Select all

/bin/sh /tmp/thebrig_install.sh /mnt/Data/jail 2

please notice the number 2 at the end.

My best sugest is that delete your actual TheBrig install, and start again, and post your step to analize.

Posted: **31 Jul 2014 23:13**

Yes im sure i installed the working branch. I started out missing the "2" at the end and didnt manage to install thebrig. When i put a 2 at the end as you mensioned above it workt like a charm. Even in the log it stated that it the installation workt fine. The problem started when i tryied to add a jail.

But as you recomed I can remove everything and start over again no problem. What is the easyest way to remove thebrig?

Found the checker and saved - removed.

Posted: **01 Aug 2014 00:04**

remember to post your steps when install thebrig to analize what happens.

Posted: **01 Aug 2014 01:05**

1. Removed everything with the included "checkbox remove thingy"
2. Removed eveything i found that had with theBrig to do over SSH. Folders tarballs.
3. Installed it all over again with SSH.
4. Pushed save in the GUI
5. Thebrig works.

Now to the jail
1. Downloaded tarballs
2. Creats new jail (owncloud)
3. Have to click apply changes

so far no problem
4.Now i click save

Boom same as before:

Code: Select all

fwrite() expects parameter 1 to be resource, boolean given in /usr/local/www/ext/thebrig/functions.inc on line 773 Warning: fwrite() expects parameter 1 to be resource, boolean given in /usr/local/www/ext/thebrig/functions.inc on line 797 Warning: fclose() expects parameter 1 to be resource, boolean given in /usr/local/www/ext/thebrig/functions.inc on line 798 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/ext/thebrig/functions.inc:719) in /usr/local/www/fbegin.inc on line 218

Posted: **01 Aug 2014 08:02**

same problem here: viewtopic.php?f=71&t=4850&p=39220&hilit ... r+1#p39220

what is the format of your disk?

Posted: **01 Aug 2014 10:26**

Yes it seems to be the same fault. Here is my disk setup where ada0 is the system disk and my destination of Data/jail.

Posted: **01 Aug 2014 12:19**

sorry, but i'm out of ideas, perhaps other power user that read this post can help you.

if not or you do not want to wait, perhaps using finch it's best option for you: viewtopic.php?f=79&t=6995

Posted: **15 Sep 2014 21:00**

Hi all,

I followed to the letter the commands of the program installation however I got an error at the end of the installation.

No input file specified.

can someone help me?

nas4free: DADOS # ./thebrig_install.sh /mnt/DADOS/Jail
[: -eq: unexpected operator
[: -eq: unexpected operator
Retrieving the most recent version of TheBrig
master.zip 100% of 181 kB 159 kBps 00m01s
Unpacking the tarball...
x README
x conf/
x conf/bin/
x conf/bin/ftp_amd64
x conf/bin/ftp_i386
x conf/bin/thebrig_fetch.sh
x conf/bin/thebrig_start.php
x conf/bin/thebrig_start.sh
x conf/bin/thebrig_stop.sh
x conf/ext/
x conf/ext/thebrig/
x conf/ext/thebrig/extensions_thebrig.php
x conf/ext/thebrig/extensions_thebrig_check.php
x conf/ext/thebrig/extensions_thebrig_config.php
x conf/ext/thebrig/extensions_thebrig_download.php
x conf/ext/thebrig/extensions_thebrig_edit.php
x conf/ext/thebrig/extensions_thebrig_tarballs.php
x conf/ext/thebrig/extensions_thebrig_tools.php
x conf/ext/thebrig/functions.inc
x conf/ext/thebrig/lang.inc
x conf/ext/thebrig/menu.inc
x conf/ext/thebrig/off_small.png
x conf/ext/thebrig/on_small.png
x conf/freebsd-update.conf
x conf/periodic.conf
x conf/portsnap.conf
x thebrig_install.sh
No input file specified.
You use fresh version

Posted: **16 Sep 2014 07:40**

zardozsan wrote: ./thebrig_install.sh /mnt/DADOS/Jail

please delete your files, and try this time adding a "2" at the end:

Code: Select all

thebrig_install.sh /mnt/DADOS/Jail 2

this time see if script install latest working version of theBring instead of master that is outdated.

PD: see if this line

master.zip 100% of 181 kB 159 kBps 00m01s

change to

working.zip 100% of 181 kB 159 kBps 00m01s

Posted: **06 Oct 2014 04:20**

Hey all,

I installed TheBrig w/o error/problem. Created the 1st full test jail and started w/o error, but when I ssh into that jail IP I can see my real NAS4Free root as oppose to the one I specified -> /mnt/data/jail/test in which in there I can see all the related FreeBSD files.

I thought my jail / should be /mnt/data/jail/test, did I miss something?

Tkx!
--Rival.

Posted: **06 Oct 2014 09:38**

BlaSTiWi wrote:I thought my jail / should be /mnt/data/jail/test, did I miss something?

yes , a jail show itself as normal root, so it's normal that show root and not /mnt/data/jail/test because jail do not know enything from top level directories from /mnt/data/jail/test (/mnt/data/jail/test is the / for a jail)

http://en.wikipedia.org/wiki/FreeBSD_jail

Posted: **06 Oct 2014 17:00**

raulfg3 wrote:yes , a jail show itself as normal root, so it's normal that show root and not /mnt/data/jail/test because jail do not know enything from top level directories from /mnt/data/jail/test (/mnt/data/jail/test is the / for a jail)

http://en.wikipedia.org/wiki/FreeBSD_jail

Ahhh I thought when I ssh into my my test jail it'll chroot into my jail root tree (which is /mnt/data/jail/test). What will happend if I install pkg or software? It'll use the /usr/local from the real root instead of the /mnt/data/jail/test root within the jail? I also saw and can login using other non-system user that I setup on the real nas4free into my jail so the jail inherited the main users which I thought it should not since it has its own /etc/passwd and all.

I guess I'm expecting ssh into my jail kinda behave like 'jexec 2 csh' [where 2 is what listed under JID when I did jls cmd).

Tkx!
--Rival.

Posted: **24 Oct 2014 09:13**

I just installed the brig and i am getting error this error in my LOGs
/mnt/pipeline/jail/conf/bin/ftp: Permission denied and I cant download the tar balls

can anyone point me in the right dirrection

XigmaNAS

[HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - The default jail manager for N

Re: [HOWTO] Install TheBrig - The default jail manager for N

Re: [HOWTO] Install TheBrig - The default jail manager for N

Re: [HOWTO] Install TheBrig - The default jail manager for N

Re: [HOWTO] Install TheBrig - The default jail manager for N

Re: [HOWTO] Install TheBrig - The default jail manager for N

Re: [HOWTO] Install TheBrig - The default jail manager for N

Re: [HOWTO] Install TheBrig - The default jail manager for N

Re: [HOWTO] Install TheBrig - The default jail manager for N

Re: [HOWTO] Install TheBrig - The default jail manager for N

Re: [HOWTO] Install TheBrig - The default jail manager for N

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F