This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!



I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!

[TheBrig] Jail couldn't be started or stopped

Jails with XigmaNAS
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
himbrr
Advanced User
Advanced User
Posts: 153
Joined: 21 Oct 2012 21:16
Location: Germany
Status: Offline

[TheBrig] Jail couldn't be started or stopped

Post by himbrr »

Hi All,

I have some issues with my jails.
The jails can't be started or stopped via TheBrig extension or manually via comandline.
I don't know why this happened suddenly, because this jails were running fine for years.

I have disabled the autostart of the jails after boot and rebooted the machine several times.
The issue is still there..

I have also tried to start the jails manually:

Code: Select all

root@nas4free ~ #  /etc/rc.d/jail onestart
Configuring jails:.
Starting jails:.
root@nas4free ~ #  jls
   JID  IP Address      Hostname                      Path
root@nas4free ~ #
Do you have any ideas, why the jails won't start?

Best regards,
himbrr
You do not have the required permissions to view the files attached to this post.
Nas4Free 9.2.0.1.972, ASUS P8H77-I, 8GB RAM, Intel Celeron CPU G530 @ 2.40GHz, 5x 2TB WD Red, 1x 60GB OCZ Vertex 2

User avatar
raulfg3
Site Admin
Site Admin
Posts: 4865
Joined: 22 Jun 2012 22:13
Location: Madrid (ESPAÑA)
Contact:
Status: Offline

Re: [TheBrig] Jail couldn't be started or stopped

Post by raulfg3 »

it's really difficult to know what's the problem is.

you fastest way to solve is to do a new fresh install, ( delete first old (actual jails), and restart N4F to be sure no trace of thebrig is still on your NAS.

PD: I suspect a data corruption of some jail files, but as i say it's really difficult to know.

Actually to do a new fresh install of thebring must be only 5 minutes, so I assume no problem for you, but remenber create one jail per service and do not reuse same jail (proto) for several services / installations.
12.1.0.4 - Ingva (revision 7743) on SUPERMICRO X8SIL-F 8GB of ECC RAM, 11x3TB disk in 1 vdev = Vpool = 32TB Raw size , so 29TB usable size (I Have other NAS as Backup)

Wiki
Last changes

HP T510

himbrr
Advanced User
Advanced User
Posts: 153
Joined: 21 Oct 2012 21:16
Location: Germany
Status: Offline

Re: [TheBrig] Jail couldn't be started or stopped

Post by himbrr »

I have reinstalled thebrig and tried to create a fresh new jail with the FreeBSD-amd64-9.3-RELEASE-base.txz archive.
After creating I have the following error:

Code: Select all

/thebrig/functions.inc on line 760 Warning: fwrite() expects parameter 1 to be resource, 
boolean given in /usr/local/www/ext/thebrig/functions.inc on line 761 Warning: fwrite() expects parameter 1 to be resource, 
boolean given in /usr/local/www/ext/thebrig/functions.inc on line 763 Warning: fwrite() expects parameter 1 to be resource, 
boolean given in /usr/local/www/ext/thebrig/functions.inc on line 766 Warning: fwrite() expects parameter 1 to be resource, 
boolean given in /usr/local/www/ext/thebrig/functions.inc on line 769 Warning: 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 
Jails still can't be started... Same issue as before.
At the weekend I will migrate to the newest nas4free version as embedded not full install. Hopefully this fix the issues...
Nas4Free 9.2.0.1.972, ASUS P8H77-I, 8GB RAM, Intel Celeron CPU G530 @ 2.40GHz, 5x 2TB WD Red, 1x 60GB OCZ Vertex 2

User avatar
raulfg3
Site Admin
Site Admin
Posts: 4865
Joined: 22 Jun 2012 22:13
Location: Madrid (ESPAÑA)
Contact:
Status: Offline

Re: [TheBrig] Jail couldn't be started or stopped

Post by raulfg3 »

Please confirm that you use working branch (alexey123) and use instructions from: viewtopic.php?f=79&t=3894

This error is from old (outdated) master fsbruva branch : https://github.com/fsbruva/thebrig/
12.1.0.4 - Ingva (revision 7743) on SUPERMICRO X8SIL-F 8GB of ECC RAM, 11x3TB disk in 1 vdev = Vpool = 32TB Raw size , so 29TB usable size (I Have other NAS as Backup)

Wiki
Last changes

HP T510

himbrr
Advanced User
Advanced User
Posts: 153
Joined: 21 Oct 2012 21:16
Location: Germany
Status: Offline

Re: [TheBrig] Jail couldn't be started or stopped

Post by himbrr »

I have reinstalled thebrig:

Code: Select all

#  fetch https://raw.github.com/fsbruva/thebrig/working/thebrig_install.sh
thebrig_install.sh                            100% of 4053  B 2271 kBps
#  chmod a+x thebrig_install.sh
#  sh thebrig_install.sh /mnt/Management/Programme/thebrig/ 2
Retrieving the testing branch as a zip file
fetch: https://github.com/fsbruva/thebrig/archive/working.zip: size of remote file is not known
working.zip                                            248 kB  563 kBps
Unpacking the tarball...
x README
x conf/
x conf/bin/
x conf/bin/change_ver.php
x conf/bin/ftp_amd64
x conf/bin/ftp_i386
x conf/bin/jail.sh
x conf/bin/thebrig_fetch.sh
x conf/bin/thebrig_ports_cron.php
x conf/bin/thebrig_start.php
x conf/bin/thebrig_start.sh
x conf/bin/thebrig_stop.sh
x conf/bin/thebrig_update_cron.php
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_fstab.php
x conf/ext/thebrig/extensions_thebrig_log.php
x conf/ext/thebrig/extensions_thebrig_manager.php
x conf/ext/thebrig/extensions_thebrig_ports.php
x conf/ext/thebrig/extensions_thebrig_tarballs.php
x conf/ext/thebrig/extensions_thebrig_tools.php
x conf/ext/thebrig/extensions_thebrig_update.php
x conf/ext/thebrig/fstab.png
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/freebsd-update_thin.conf
x conf/make.conf
x conf/periodic.conf
x conf/portsnap.conf
x conf/sbin/
x conf/sbin/freebsd-update
x conf/sbin/portsnap
x thebrig_install.sh
Hello new user, We will install TheBrig now
Renaming 64 bit ftp binary
Congratulations! Thebrig installed . Navigate to rudimentary config tab and push Save
Still the same error on creating jails:

Code: Select all

/thebrig/functions.inc on line 760 Warning: fwrite() expects parameter 1 to be resource, boolean given in /usr/local/www/ext/thebrig/functions.inc on line 761 Warning: fwrite() expects parameter 1 to be resource, boolean given in /usr/local/www/ext/thebrig/functions.inc on line 763 Warning: fwrite() expects parameter 1 to be resource, boolean given in /usr/local/www/ext/thebrig/functions.inc on line 766 Warning: fwrite() expects parameter 1 to be resource, boolean given in /usr/local/www/ext/thebrig/functions.inc on line 769 Warning: 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 
Nas4Free 9.2.0.1.972, ASUS P8H77-I, 8GB RAM, Intel Celeron CPU G530 @ 2.40GHz, 5x 2TB WD Red, 1x 60GB OCZ Vertex 2

User avatar
raulfg3
Site Admin
Site Admin
Posts: 4865
Joined: 22 Jun 2012 22:13
Location: Madrid (ESPAÑA)
Contact:
Status: Offline

Re: [TheBrig] Jail couldn't be started or stopped

Post by raulfg3 »

Giveme some time to do a new fresh install on a test machine and see if I can reproduce it.

In the mean while, try to create a jail using BSD9.2 instead of BSD 9.3 Try FreeBSD-amd64-9.2-RELEASE-base.txz this time.
12.1.0.4 - Ingva (revision 7743) on SUPERMICRO X8SIL-F 8GB of ECC RAM, 11x3TB disk in 1 vdev = Vpool = 32TB Raw size , so 29TB usable size (I Have other NAS as Backup)

Wiki
Last changes

HP T510

himbrr
Advanced User
Advanced User
Posts: 153
Joined: 21 Oct 2012 21:16
Location: Germany
Status: Offline

Re: [TheBrig] Jail couldn't be started or stopped

Post by himbrr »

Still have the same issue with 9.2

Code: Select all

/thebrig/functions.inc on line 760 Warning: fwrite() expects parameter 1 to be resource, boolean given in /usr/local/www/ext/thebrig/functions.inc on line 761 Warning: fwrite() expects parameter 1 to be resource, boolean given in /usr/local/www/ext/thebrig/functions.inc on line 763 Warning: fwrite() expects parameter 1 to be resource, boolean given in /usr/local/www/ext/thebrig/functions.inc on line 766 Warning: fwrite() expects parameter 1 to be resource, boolean given in /usr/local/www/ext/thebrig/functions.inc on line 769 Warning: 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 
I really hope that the fresh install of nas4free at the weekend will help...
Nas4Free 9.2.0.1.972, ASUS P8H77-I, 8GB RAM, Intel Celeron CPU G530 @ 2.40GHz, 5x 2TB WD Red, 1x 60GB OCZ Vertex 2

Post Reply

Return to “Jails”