jistme wrote:I hope you don't mind that I chose to shutdown my own brain for this exercise
Haha no problem at all!
Although sometimes trying to think of clever ideas yourself makes you learn new things completely unrelated! Or is that just me? haha
jistme wrote:The new jail shows up correctly, but I can't get it started, it will remain 'stopped'.
This is usually due to incorrect network config, something as simple as missing the subnet at the end "/24" or fstab configuration in thebrig gui. You can fix that by running this command (inside the host system and replacing "owncloud" with your jail name):
Then make sure jail settings are correct and it should start up fine
_______________________________________________________________________________________
jistme wrote:restarted nf4, started the jail manually (it doesn't seem to start automatically although that is set)
This one is a bit decieving, you have to enable 2 things for automatic startups.
First thing is the "Allow start all jails" in the Globals section on the main webgui page of the brig
And second thing is the "Start on boot" setting ticked inside of the jails settings.
_______________________________________________________________________________________
Just a thought, potentially not related to any problems the least bit:
Not sure what router you are using/how many devices you have connected to it or however else you have it set up but some routers start assigning addresses at 192.168.1.100, other routers start at 192.168.1.2 etc. so depending on your setup it may be worth trying the higher ranges? Such as 192.168.1.200 and upwards for jails. If your jail attempts to use an ip that the router has already assigned to another device, bad things happen
_______________________________________________________________________________________
You have internet connectivity im guessing otherwise you wouldnt be able to download the script
Various things you can try:
Try 'pkg install nano' inside the host system to see if you can get packages there.
Double check your jail settings to make sure IP is set up right (Right down to the subnet [192.168.2.101/24])
Sometimes the jail doesn't always save the network settings properly so i tend to create the jail then go back in to the settings to make sure the network ip etc. is set up correctly.
Inside the jail try these things:
Make sure the jail itself can reach the internet
(Might be pkg upgrade -f instead)
Try the old pkg_add tool:
_______________________________________________________________________________________
That's all i got right now without rebooting my nas, accidentally locked myself out xD (partner will kill me if i do that before her movie finishes!)
We can also try installing directly from the ports tree (Will update this post soon with how to do that)
Alright, here we go for the port install:
First, head to thebrig gui, click on the "Updates" tab then "Central Ports"
Click "Fetch & Update" (I can't remember if there was a progress bar for this or not) once it's done, after refreshing the page the "Current Status" will say something like:
Code: Select all
The latest snapshot available for download is dated: Sat Mar 12 22:36:34 AEST 2016
You have downloaded a snapshot that was released: Tue Feb 16 00:20:58 AEST 2016
The last time you applied a downloaded snapshot was: Tue Feb 16 00:42:45 AEST 2016
Now we tick the box for your owncloud jail and hit "Save" down the bottom left.
You shouldn't have to restart the jail for it to take effect but for good measure, do that before proceeding.
Once that's all done, log in to the jail and run these commands (Might not need the first 2 lines, can't remember for jails):
Code: Select all
portsnap fetch extract
portsnap fetch update
cd /usr/ports/ports-mgmt/pkg && make UPGRADEPKG=1 install clean
_______________________________________________________________________________________
Surely something above will work! haha
