8.2.0 Beta 3 Unable to start plugins

Status
Not open for further replies.

Vanyo

Dabbler
Joined
Oct 2, 2011
Messages
45
I created a network interface and the two volumes for the jail, but when I wanted to start the service, the following occured:

Apr 24 09:34:43 NAS init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 secs
Apr 24 09:35:17 NAS init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 secs
Apr 24 09:35:51 NAS init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 secs
Apr 24 09:35:54 NAS notifier: cp: /mnt/Disk1/jail/software/etc/resolv.conf: No such file or directory
Apr 24 09:35:54 NAS notifier: security.jail.allow_raw_sockets: 0 -> 1
Apr 24 09:35:54 NAS notifier: Configuring jails: sysvipc_allow=YES.
Apr 24 09:35:54 NAS notifier: Starting jails:df: /mnt/Disk1/jail/software/dev: No such file or directory
Apr 24 09:35:55 NAS notifier: mount: /mnt/Disk1/jail/software/dev: No such file or directory
Apr 24 09:35:55 NAS root: /etc/rc.d/jail: WARNING: devfs_domount(): Unable to mount devfs on /mnt/Disk1/jail/software/dev
Apr 24 09:35:55 NAS notifier: /etc/rc.d/jail: WARNING: devfs_domount(): Unable to mount devfs on /mnt/Disk1/jail/software/dev
Apr 24 09:35:55 NAS root: /etc/rc.d/jail: WARNING: devfs_mount_jail: devfs was not mounted on /mnt/Disk1/jail/software/dev
Apr 24 09:35:55 NAS notifier: /etc/rc.d/jail: WARNING: devfs_mount_jail: devfs was not mounted on /mnt/Disk1/jail/software/dev
Apr 24 09:35:55 NAS notifier: cd: can't cd to /mnt/Disk1/jail/software/dev
Apr 24 09:35:55 NAS notifier: ln: log: Read-only file system
Apr 24 09:35:55 NAS notifier: cannot start jail "software":
Apr 24 09:35:55 NAS notifier: jail: getpwnam: root: No such file or directory
Apr 24 09:35:55 NAS notifier: .
Apr 24 09:35:56 NAS notifier: Stopping jails: cannot stop jail software. No jail id in /var/run
Apr 24 09:35:56 NAS notifier: .
 

Vanyo

Dabbler
Joined
Oct 2, 2011
Messages
45
I just followed the description @ http://doc.freenas.org/index.php/Plugins.

No victory, even if I create the dir, I get some errors (btw, why is the getty repeating...???):

Apr 24 19:27:19 NAS init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 secs
Apr 24 19:27:53 NAS init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 secs
Apr 24 19:30:08 NAS last message repeated 4 times
Apr 24 19:38:35 NAS last message repeated 15 times
Apr 24 19:38:58 NAS notifier: cp: /mnt/Disk1/jail/software/etc/resolv.conf: No such file or directory
Apr 24 19:38:58 NAS notifier: security.jail.allow_raw_sockets: 1 -> 1
Apr 24 19:38:58 NAS notifier: Configuring jails:.
Apr 24 19:38:58 NAS notifier: Starting jails: cannot start jail "software":
Apr 24 19:38:58 NAS notifier: jail: getpwnam: root: No such file or directory
Apr 24 19:38:58 NAS notifier: .
Apr 24 19:38:59 NAS notifier: Stopping jails: cannot stop jail software. No jail id in /var/run
Apr 24 19:38:59 NAS notifier: .
Apr 24 19:39:08 NAS init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 secs
 

William Grzybowski

Wizard
iXsystems
Joined
May 27, 2011
Messages
1,754
Try

# mkdir /mnt/Disk1/jail/software/etc

But I dont think it will work, you've done something wrong...

Delete the jail and start over.
 

Vanyo

Dabbler
Joined
Oct 2, 2011
Messages
45
Re-created the interface, the datasets, and the PBI Jail, but the results are the same. Any other idea?
 

Vanyo

Dabbler
Joined
Oct 2, 2011
Messages
45
These dirs exist on the jail dataset (no dev created):

[root@NAS /mnt/Disk1/jail/software]# ls
.auto-external-links etc sbin
.headerdir include share
.pbi-hash-list info transmission
.sbin lib transmissionUI
bin libdata tweak-rcconf
control libexec usr
control.py man www
default.png mnt
 

ppmax

Contributor
Joined
May 16, 2012
Messages
111
Hi--

Just wanted to add a datapoint here...

I followed the instructions here explicitly:
http://doc.freenas.org/index.php/Plugins

Im on a brand spanking new FreeNAS-8.2.0-BETA3-x64 (r11188) install, and I have created a few ZFS datasets:
volume1 /mnt/volume1 156.0 MiB (0%) 1.8 TiB 1.8 TiB HEALTHY
volume1/jail /mnt/volume1/jail 31.5 KiB (0%) 10.0 GiB 10.0 GiB HEALTHY
volume1/jail/software /mnt/volume1/jail/software 31.5 KiB (0%) 5.0 GiB 5.0 GiB HEALTHY

volume1 is a 4 disk RAIDZ2

I have a static lease for my host (freeness) at 192.168.0.14. My pfsense router hands out the static lease and provides default gateway and nameservers and I can ping other machines on my network while ssh'd into my freenas box. Network and routing is A-OK.

I created a network interface for the jail:
em0 jail True 192.168.0.15/24 False

I went to Services and created a jail as described in the link above. The plugins_jail-8.2-x64.pbi uploads fine...but then at the end I get a stream of errors in the messages log file (see below). I've tried this several times now--it seems there are issues with permissions when installing the plugins_jail-8.2-x64.pbi.

I also tried creating the jail and software datasets and then changing permissions recursively to root:wheel 777 (via the GUI) before uploading the pbi--but the result was the same. FWIW: volume1 permissions were changed via the GUI to root:wheel 777 when I created volume1.

Strangely, I was able to successfully install the PBI while testing freeNAS in a VM...

Finally, while ssh'd into my freenas host, I run jls and don't see any jails. I guess this is obvious, since the plugins_jail-8.2-x64.pbi didn't seem to install properly.

Here is the output from tail -f /var/log/mesasges:
May 30 21:46:43 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/var/empty: Operation not permitted
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/var: Directory not empty
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/libexec/ld-elf32.so.1: Operation not permitted
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/libexec/ld-elf.so.1: Operation not permitted
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/libexec: Directory not empty
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/sbin/init: Operation not permitted
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/sbin: Directory not empty
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/bin/rcp: Operation not permitted
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/bin: Directory not empty
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/lib32/librt.so.1: Operation not permitted
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/lib32/libcrypt.so.5: Operation not permitted
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/lib32/libc.so.7: Operation not permitted
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/lib32/libthr.so.3: Operation not permitted
May 30 21:46:47 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/lib32: Directory not empty
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/lib/librt.so.1: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/lib: Directory not empty
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/ypchsh: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/su: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/login: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/ypchfn: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/passwd: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/ypchpass: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/opiepasswd: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/chfn: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/crontab: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/chpass: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/yppasswd: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/rsh: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/chsh: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/opieinfo: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin/rlogin: Operation not permitted
May 30 21:46:50 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr/bin: Directory not empty
May 30 21:46:51 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/usr: Directory not empty
May 30 21:46:51 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/lib/libc.so.7: Operation not permitted
May 30 21:46:51 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/lib/libcrypt.so.5: Operation not permitted
May 30 21:46:51 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/lib/libthr.so.3: Operation not permitted
May 30 21:46:51 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64/lib: Directory not empty
May 30 21:46:51 freenas notifier: mv: /mnt/volume1/jail/plugins_jail-amd64: Directory not empty
May 30 21:46:51 freenas notifier: mv: /bin/rm /mnt/volume1/jail/plugins_jail-amd64: terminated with 1 (non-zero) status
May 30 21:46:52 freenas notifier: Waiting for http... Done.


Any suggestions?

thx--
PP
 

ppmax

Contributor
Joined
May 16, 2012
Messages
111
I've done that multiple times. Are you suggesting to not use the names jail and software?

Thanks for the *quick* reply! ;)

PP
 

ppmax

Contributor
Joined
May 16, 2012
Messages
111
I've done that multiple times. Are you suggesting to not use the names jail and software?

Thanks for the *quick* reply! ;)

PP

Interesting. I trashed the datasets and created 2 new datasets named plugins_jail and plugins_software, then created a new jail named plugins successfully. Thanks for the suggestion William.

What causes the collisions with dataset names?

thx
PP
 
Status
Not open for further replies.
Top