Starting Jail / Plugins Service fails

[EasyNT]

Hello

I've been trying to create a jail with FreeNAS-8.3.1-RELEASE-p2-x64 (r12686+b770da6_dirty), but it always fails. I've tried it with two fresh images on a USB stick.

I get things like:


Jun 30 14:43:49 freenas notifier: security.jail.allow_raw_sockets: 0 -> 1
Jun 30 14:43:49 freenas notifier: Configuring jails: sysvipc_allow=YES.
Jun 30 14:43:49 freenas notifier: Starting jails: cannot start jail "test":
Jun 30 14:43:49 freenas notifier: .
Jun 30 14:43:49 freenas kernel: bridge0: Ethernet address: 02:ce:8f:5b:7c:00
Jun 30 14:43:49 freenas kernel: epair0a: Ethernet address: 02:01:29:00:06:0a
Jun 30 14:43:49 freenas kernel: epair0b:
Jun 30 14:43:49 freenas kernel: Ethernet address: 02:01:29:00:07:0b
Jun 30 14:43:49 freenas notifier: jexec: execvp(): ifconfig: Permission denied
Jun 30 14:43:49 freenas kernel:
Jun 30 14:43:49 freenas kernel: epair0a: link state changed to UP
Jun 30 14:43:49 freenas kernel: epair0b: link state changed to UP
Jun 30 14:43:49 freenas kernel: epair0a: promiscuous mode enabled
Jun 30 14:43:49 freenas notifier: jexec: execvp(): route: Permission denied
Jun 30 14:43:49 freenas notifier: jexec: execvp(): /bin/sh: Permission denied
Jun 30 14:43:49 freenas kernel: bge0: promiscuous mode enabled
Jun 30 14:43:50 freenas notifier: Stopping jails: cannot stop jail test. No jail id in /var/run

Is this something seen before? Does anybody know a workarround? It seems there's a problem with the network, i.e. the jail seems to fail when it should set it's ip address...


Thanks, Juerg

 

[EasyNT]

Ok folks, never mind. The problem was that I initially set my ZFS volume to exec=off which then was inherited by the jail datasets. I use to set the exec=off flag for data only volumes as it prevents infected files from spreading, but when I created the ZFS volume, I didn't had in mind that I would possibly create and store a jail on the same ZFS volume...