Unable to start the Plugin service

Status
Not open for further replies.

csani

Cadet
Joined
Jan 21, 2013
Messages
4
Hello all,

I have recently joined the crowd, still have a lot to learn :) For the most part I was able to do everything i wanted but the Plugin section got the best of me.

As many before me I am unable to start the service even though i have a jail and a valid minidlna pbi file. Here is what my messages file looks like after a reboot and an attempt to start the service:

Jan 21 13:01:13 freenas ntpd[1672]: time reset +0.648202 s
Jan 21 13:02:44 freenas notifier: security.jail.allow_raw_sockets: 0 -> 1
Jan 21 13:02:44 freenas notifier: Configuring jails: sysvipc_allow=YES.
Jan 21 13:02:44 freenas notifier: Starting jails:df: /mnt/volume1/jail01/new/dev: No such file or directory
Jan 21 13:02:44 freenas notifier: mount: /mnt/volume1/jail01/new/dev: No such file or directory
Jan 21 13:02:44 freenas root: /etc/rc.d/jail: WARNING: devfs_domount(): Unable to mount devfs on /mnt/volume1/jail01/new/dev
Jan 21 13:02:44 freenas notifier: /etc/rc.d/jail: WARNING: devfs_domount(): Unable to mount devfs on /mnt/volume1/jail01/new/dev
Jan 21 13:02:44 freenas root: /etc/rc.d/jail: WARNING: devfs_mount_jail: devfs was not mounted on /mnt/volume1/jail01/new/dev
Jan 21 13:02:44 freenas notifier: /etc/rc.d/jail: WARNING: devfs_mount_jail: devfs was not mounted on /mnt/volume1/jail01/new/dev
Jan 21 13:02:44 freenas notifier: ln: /mnt/volume1/jail01/new/dev/log: No such file or directory
Jan 21 13:02:44 freenas notifier: cannot start jail "new":
Jan 21 13:02:44 freenas notifier: .
Jan 21 13:02:44 freenas notifier: jexec: execvp(): ifconfig: No such file or directory
Jan 21 13:02:44 freenas kernel: bridge0: Ethernet address: 02:8f:32:2b:d6:00
Jan 21 13:02:44 freenas kernel: epair0a: Ethernet address: 02:a1:d2:00:07:0a
Jan 21 13:02:44 freenas kernel: epair0b: Ethernet address: 02:a1:d2:00:08:0b
Jan 21 13:02:44 freenas kernel: epair0a: link state changed to UP
Jan 21 13:02:44 freenas kernel: epair0b: link state changed to UP
Jan 21 13:02:44 freenas kernel: epair0a: promiscuous mode enabled
Jan 21 13:02:44 freenas notifier: jexec: execvp(): route: No such file or directory
Jan 21 13:02:44 freenas kernel: em0: link state changed to DOWN
Jan 21 13:02:44 freenas notifier: jexec: execvp(): /bin/sh: No such file or directory
Jan 21 13:02:44 freenas kernel: em0: promiscuous mode enabled
Jan 21 13:02:45 freenas notifier: Stopping jails: cannot stop jail new. No jail id in /var/run
Jan 21 13:02:45 freenas notifier: .
Jan 21 13:02:48 freenas kernel: em0: link state changed to UP
[root@freenas] /var/log#



Any help would greatly improve the pase of my evolution :)

Thanks!
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
And which version of FreeNAS are you running?

Did you follow the instructions for installing the jail? Instructions are in the manual. And I assume you downloaded the jail PBI from them same area that you grabbed FreeNAS?
 

csani

Cadet
Joined
Jan 21, 2013
Messages
4
hey Joe,

I am using 8.3.0

I was finally able to start the Plugin service but when attempting to start the miniDLNA i get the omnious error "MiniDLNA data did not validate, configure it first." I have rebooted several times, reinstalled the pbi and still the minidlna does not show up in the tree under services. From what i have been reading i should configure it there before starting the service.

About to give up on the idea this will ever work :(
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
So once you have the jail plugin running you will install the MiniDLNA plugin. Once it's installed you should have a drop down under Services → Plugins → Management → MiniDLNA. See page 183 of the users guide.

Actually installation and configuration is a breeze for MiniDLNA now days. Last year is wasn't like that and it was all manual changes in a few locations. I would prefer MiniDLNA be an installed part of FreeNAS but the folks programming it would prefer not doing it but I see their point.

Hope this helps.
 

csani

Cadet
Joined
Jan 21, 2013
Messages
4
Thanks for your efforts Joe.

Unfortunately even with the minidlna installed i do not have any reference to it under Services → Plugins → Management.

Capture.JPG


Why?!
 

Attachments

  • Capture.JPG
    Capture.JPG
    33.5 KB · Views: 292

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
I'm not sure what is going on there but I've never seen anyone have this type of problem before.

Just to cover all the bases, you downloaded FreeNAS 8.3.0-Release and installed the plugins from that folder? Did you use the 64 bit version or 32 bit version? I'd like to recreate your problem, could you give me the download path of the files you grabbed?
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
I also grabbed and just tested the 8.3.1-Beta2 (64-bit) and it works fine as well, with respect to Jail and MiniDLNA loading and configuring.

If you are running the 64 bit version and you are stuck, I'm not sure I can help you any further as without controlling your FreeNAS system, I cannot figure out what is going on.
 

raymonvdm

Dabbler
Joined
Aug 24, 2011
Messages
14
I also have an issue when starting the jail it sometime will not start because of errors in /etc/rc.conf

Code:
4"
5
"6


The errors seem to occur when creating the jail, when i delete the unwanted characters the service starts fine.

The config when successful starting (/etc/rc.conf)

Code:
jail_jail_rootdir="/mnt/tank/jail/jail"
jail_jail_hostname="jail"
jail_jail_devfs_enable="YES"
jail_jail_devfs_ruleset="devfsrules_jail"
jail_jail_procfs_enable="YES"
jail_jail_mount_enable="YES"
jail_jail_vnet_enable="YES"
jail_jail_flags="-l -U root -c persist"
jail_jail_exec_afterstart0="ifconfig lo0 127.0.0.1"
jail_jail_exec_start="/bin/sh /dev/null"
jail_sysvipc_allow="YES"
jail_list="jail"
jail_v2_enable="YES"
jail_enable="YES"
jail_jail_exec_poststop0="ifconfig bridge4 destroy"
jail_jail_exec_poststop1="ifconfig epair4a destroy"
jail_jail_exec_poststop2="arp -d 192.168.110.191"
jail_jail_exec_poststop3="jail -r 1



But the ip adres which is choosen for the jail is not up (another ip wil have same issue)

The issue really seem to be with bringing up the secondary ip
 

William Grzybowski

Wizard
iXsystems
Joined
May 27, 2011
Messages
1,754
This is all fucked up.

Paste the screenshot with the settings for Plugins service and the Interfaces screen.

After this, stop the Plugins service, restart the box, edit /etc/syslog.conf and uncomment the .*debug line, run service syslogd restart.

Once it is done paste:
# ifconfig -a
# netstat -rn

Then try to start the Plugins service from GUI and after this paste again:

# ifconfig -a
# netstat -rn
# jexec `jls jid` ifconfig -a

And attach /var/log/debug.log

(Use pastebin.com)
 

raymonvdm

Dabbler
Joined
Aug 24, 2011
Messages
14
I have rebooted the machine and after the reboot i had an extra interface bridge0 with a third ip adres.(not shure if i did this manualy) After that it is possible to add the second ip (the one from the jail) and the jail is working.

I have now successfully installed two plugins and all

Note: I deleted the garbage in /etc/rc.conf serveral times
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
It gets frustrating at times trying to help people doesn't it.
 

csani

Cadet
Joined
Jan 21, 2013
Messages
4
This is all fucked up.

Paste the screenshot with the settings for Plugins service and the Interfaces screen.

After this, stop the Plugins service, restart the box, edit /etc/syslog.conf and uncomment the .*debug line, run service syslogd restart.

Once it is done paste:
# ifconfig -a
# netstat -rn

Then try to start the Plugins service from GUI and after this paste again:

# ifconfig -a
# netstat -rn
# jexec `jls jid` ifconfig -a

And attach /var/log/debug.log

(Use pastebin.com)


Will, here you go, please let me know what I am doing wrong...

fn1.JPG fn2.JPG fn3.JPG

after reboot:

[root@freenas] ~# ifconfig -a
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether f4:6d:04:9b:86:e7
inet 192.168.2.20 netmask 0xffffff00 broadcast 192.168.2.255
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
re0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
ether f4:6d:04:9b:81:63
media: Ethernet autoselect (10baseT/UTP <half-duplex>)
status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>

[root@freenas] ~# netstat -rn
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.2.1 UGS 0 22 em0
127.0.0.1 link#5 UH 0 6094 lo0
192.168.2.0/24 link#1 U 0 982 em0
192.168.2.20 link#1 UHS 0 0 lo0

Internet6:
Destination Gateway Flags Netif Expire
::/96 ::1 UGRS lo0
::1 link#5 UH lo0
::ffff:0.0.0.0/96 ::1 UGRS lo0
fe80::%lo0/64 link#5 U lo0
fe80::1%lo0 link#5 UHS lo0
ff01::%lo0/32 fe80::1%lo0 U lo0
ff02::%lo0/32 fe80::1%lo0 U lo0
[root@freenas] ~#

After start of Plugins:


[root@freenas] ~# ifconfig -a
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=42098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO>
ether f4:6d:04:9b:86:e7
inet 192.168.2.20 netmask 0xffffff00 broadcast 192.168.2.255
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
re0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
ether f4:6d:04:9b:81:63
media: Ethernet autoselect (10baseT/UTP <half-duplex>)
status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:8f:32:2b:d6:00
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 1 priority 128 path cost 200000
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 7 priority 128 path cost 2000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:2a:7a:00:07:0a
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
[root@freenas] ~#

[root@freenas] ~# netstat -rn
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.2.1 UGS 0 27 em0
127.0.0.1 link#5 UH 0 6523 lo0
192.168.2.0/24 link#1 U 0 1109 em0
192.168.2.20 link#1 UHS 0 0 lo0

Internet6:
Destination Gateway Flags Netif Expire
::/96 ::1 UGRS lo0
::1 link#5 UH lo0
::ffff:0.0.0.0/96 ::1 UGRS lo0
fe80::%lo0/64 link#5 U lo0
fe80::1%lo0 link#5 UHS lo0
ff01::%lo0/32 fe80::1%lo0 U lo0
ff02::%lo0/32 fe80::1%lo0 U lo0
[root@freenas] ~#


[root@freenas] ~# jexec 1 ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:2a:7a:00:08:0b
inet 192.168.2.21 netmask 0xffffff00 broadcast 192.168.2.255
inet6 fe80::2a:7aff:fe00:80b%epair0b prefixlen 64 scopeid 0x2
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
[root@freenas] ~#


Please see that even if the plugins service is now running the plugins arenot present in the tree under Services->Plugins
 

William Grzybowski

Wizard
iXsystems
Joined
May 27, 2011
Messages
1,754
Could not find anything strange.

Does /etc/rc.conf get messed up everytime you stop/start the plugin service?
 
Status
Not open for further replies.
Top