Plugins service problems

Status
Not open for further replies.

ajgraham

Cadet
Joined
Jun 24, 2012
Messages
1
Hi all,
I'm having a few issues with FreeNAS 8.2 beta4 which I just can't seem to overcome. I originally followed this http://www.youtube.com/watch?v=07yR0igpeao video guide to set the plugins so that it should function. Having read a thread here though apparently the Alias on the network interface isn't meant to be set for the beta4 version so I've now deleted this Alias and the interface ip address is set to 192.168.1.101. I've setup the Plugin settings to use 192.168.1.102

The Plugin service starts and I can install plugins, but if I try to start something (tried Firefly and MiniDLNA) it just says "Some error occurred". I'm not sure what else to do other than to reset everything and try again

log from /var/log/messages:
Jun 24 19:29:13 freenas manage.py: [services.views:79] Couldn't retrieve http://
192.168.1.101:80/plugins/firefly/_s/status: HTTP Error 502: Bad Gateway
Jun 24 19:29:13 freenas manage.py: [services.views:79] Couldn't retrieve http://
192.168.1.101:80/plugins/minidlna/_s/status: HTTP Error 502: Bad Gateway
Jun 24 19:29:43 freenas kernel: Freed UMA keg was not empty (336 items). Lost 2
pages of memory.
Jun 24 19:29:43 freenas kernel: Freed UMA keg was not empty (33 items). Lost 3
pages of memory.
Jun 24 19:29:43 freenas kernel: Freed UMA keg was not empty (8 items). Lost 2 p
ages of memory.
Jun 24 19:29:43 freenas kernel: Freed UMA keg was not empty (22 items). Lost 2
pages of memory.
Jun 24 19:29:44 freenas kernel: epair0a: promiscuous mode disabled
Jun 24 19:29:44 freenas kernel: epair0a: link state changed to DOWN
Jun 24 19:29:44 freenas kernel: epair0b: link state changed to DOWN
Jun 24 19:29:44 freenas notifier: Stopping jails: software192.168.1.102 (192.168
.1.102) deleted
Jun 24 19:29:44 freenas notifier: .
Jun 24 19:29:48 freenas notifier: security.jail.allow_raw_sockets: 1 -> 1
Jun 24 19:29:48 freenas notifier: Configuring jails:.
Jun 24 19:29:48 freenas notifier: Starting jails: software.
Jun 24 19:29:48 freenas notifier: ifconfig: options=c019b<RXCSUM,TXCSUM,VLAN_MTU
,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>: bad value
Jun 24 19:29:48 freenas kernel: bridge0: Ethernet address: ba:a8:39:b4:70:bf
Jun 24 19:29:48 freenas kernel: epair0a: Ethernet address: 02:e9:3f:00:04:0a
Jun 24 19:29:48 freenas kernel: epair0b: Ethernet address: 02:e9:3f:00:05:0b
Jun 24 19:29:48 freenas kernel: epair0a: link state changed to UP
Jun 24 19:29:48 freenas kernel: epair0b: link state changed to UP
Jun 24 19:29:48 freenas notifier: ifconfig: options=c019b<RXCSUM,TXCSUM,VLAN_MTU
,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>: bad value
Jun 24 19:29:48 freenas kernel: epair0a: promiscuous mode enabled


Any help is appreciated,
Alex
 

AlunS

Cadet
Joined
Jun 26, 2012
Messages
9
I'm having the same problems with both miniDLNA and Transmission. I've gone through the process of deleting/re-installing both the jail and the plugins so many times now it's unreal, and every time things go a little differently. Sometimes the plugin installs fine, works for a bit and after a while refuses to be either started or stopped or configured, coming up with the infamous "An error as occurred" message. Sometimes the text of the plugin appears in the menu tree but without the 'flag' icon, and refuses to cooperate at all, and sometimes I don't even get that far.

The jail is accessible at IP level from the host and vice versa, so that's not the problem (managed to discover that the setting of an alias isn't necessary after much experimenting.)
 

talon42

Dabbler
Joined
May 15, 2012
Messages
33
Same issue here. There seems to be some weird plugin/jail issues. I just tried to access the plugin UI and it rebooted the system. On reboot, neither Firefly or Minidlna are started up. I can't even access the services using the jail ip. nmap shows the host is down even though this had just been working.

I just tried turned off the service to change the IP. When I turned it on, it crashed and rebooted.

I am now seeing that even though all three services are on (transmission, firefly and minidlna) , the plugin tree only shows the firefly and transmission plugins. Refresh didn't work . I had to disabled and reenable the minidlna plugin.
 

AlunS

Cadet
Joined
Jun 26, 2012
Messages
9
I can only speak for myself but I'm running x64 on an HP N40L microserver with 8GB RAM. I've made a little progress in as much as I've reinstalled yet again from scratch , the only difference is that this time I've not configured CIFS yet, and now I can successfully stop/start both MiniDLNA and Transmission successfully and configure them too. All other times I've gone and configured CIFS before the plugins, but I don't know if that has any relevance. I'll configure CIFS later and see if that breaks things.
 

AlunS

Cadet
Joined
Jun 26, 2012
Messages
9
I spoke too soon :( I just started it up again to try and configure CIFS and noticed the MiniDLNA item was missing from the plugin configuration menu. I could start the plugin itself though (even though it should start up automatically but hadn't). Tried stopping and starting the plugin service and got a Fatal Trap 12, something that's happened a few times recently, mostly on shutdown though. Not looking good.

Regarding the Fatal Trap 12's, I read somewhere that there are problems reported with the FreeBSD driver for integrated NIC (bge0) in the HP N40L .. is that the case? I've run memtest86+ overnight with no problems so I think I can rule out any memory problems.
 

William Grzybowski

Wizard
iXsystems
Joined
May 27, 2011
Messages
1,754
The fatal trap panics are a known issue, it may happen if you stop the jail.

If you have time step by on #freenas at irc.freenode.net. It is very stressing and time consuming to do support over forum.
 

AlunS

Cadet
Joined
Jun 26, 2012
Messages
9
Just to update: RC1 is giving me exactly the same problems. Installed everything from scratch, installed miniDLNA and it worked for an hour or so and then :poof: the icon on the configuration item disappeared, "An error occurred" when you try and configure it and you can't stop/start it either. Deleted the plugin, and the jail, and installed them all over again and it can't be configured at all. The only way to get it working, for a while at least, is to revert to factory settings and do a clean install, but it doesn't last.
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
I think there are definitely some glitches in the way plugins work in the jail, you should TRY creating a plugin!! Ugghh

Anyway, I suspect that when you delete a jail without first deleting the plugins, the FreeNAS database still has the info about those plugins, that's why a factory reset works.

So, before you delete a jail, delele the plugins first. I'm sure this will be fixed.
 

William Grzybowski

Wizard
iXsystems
Joined
May 27, 2011
Messages
1,754
Please paste:

# ifconfig -a
# jexec 1 ifconfig -a
# jexec 1 ps axuww
# jexec 1 sockstat -4

Once the errors start happenning again...
 

AlunS

Cadet
Joined
Jun 26, 2012
Messages
9
OK, will do. I've just done yet another clean install, and am making sure I've got a fully working system without plugins, then I'll save the config and try and reproduce. I've no problems with pinging the host, the jail and external IP's from anywhere, so I'm not sure connectivity is the problem but I'll let you know ASAP.
 

Spocksbeer

Cadet
Joined
Jun 6, 2011
Messages
6
I'm having similar problems, except without the intermediate step of minidlna working temporarily - it simply wont start at all. Installs fine, no errors in the UI, but fails to add an item to the "Services" tree and gives "some error occured" when attempting to start.

This is an x64 upgrade straight from 8.0.2 (so far, sucessful), so no prior plugin experience. The jail is up and running fine, and responds to pings quite happily. Hardware is an HP NL36, 8GB.

ifconfig -a:

Code:
bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=c0099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO,LINK STATE>
        ether 68:b5:99:72:cc:71
        inet 192.168.178.31 netmask 0xffffff00 broadcast 192.168.178.255
        inet6 fe80::6ab5:99ff:fe72:cc71%bge0 prefixlen 64 scopeid 0x1
        inet6 2001:44b8:513a:7600:6ab5:99ff:fe72:cc71 prefixlen 64 autoconf
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
        media: Ethernet autoselect (100baseTX <full-duplex,flowcontrol,rxpause,txpause>)
        status: active
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 0x2
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 96:10:e7:1e:cc:c2
        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: bge0 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 4 priority 128 path cost 2000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:0b:55:00:04:0a
        inet6 fe80::b:55ff:fe00:40a%epair0a prefixlen 64 scopeid 0x4
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active


jexec 4 ifconfig -a:

Code:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:0b:55:00:05:0b
        inet 192.168.178.201 netmask 0xffffff00 broadcast 192.168.178.255
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>



jexec 4 ps axuww:

Code:
USER   PID %CPU %MEM   VSZ   RSS  TT  STAT STARTED      TIME COMMAND
root  9120  0.0  0.0  5404   988  ??  SsJ  10:11AM   0:00.02 /usr/sbin/syslogd -ss
root  9252  0.0  0.0  5432  1140  ??  IsJ  10:11AM   0:00.03 /usr/sbin/cron -s
root 13433  0.0  0.0  5484   892   1  R+J  12:53PM   0:00.00 ps axuww


jexec 4 sockstat -4:
Code:
sockstat: struct xinpgen size mismatch
 

AlunS

Cadet
Joined
Jun 26, 2012
Messages
9
OK, a different scenario this time. I installed the jail, then minidlna and this time I couldn't even configure it (Sorry, an error occurred!), let alone start it (Some error occurred). Host IP is 192.168.11.100 and jail IP is 192.168.11.101. I can ping back and forth between host, jail and rest of local network no problem. Machine is an HP Proliant Microserver N40L.
Code:
[root@freenas] ~# ifconfig -a
bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=c0099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE>
        ether e8:39:35:ee:1d:f6
        inet 192.168.11.100 netmask 0xffffff00 broadcast 192.168.11.255
        media: Ethernet autoselect (100baseTX <full-duplex,flowcontrol,rxpause,txpause>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        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 a2:ec:7b:67:2e:1e
        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: bge0 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 4 priority 128 path cost 2000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:c8:aa:00:04:0a
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active

Code:
[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
        ether 02:c8:aa:00:05:0b
        inet 192.168.11.101 netmask 0xffffff00 broadcast 192.168.11.255
        inet6 fe80::c8:aaff:fe00:50b%epair0b prefixlen 64 scopeid 0x2
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active

Code:
[root@freenas] ~# jexec 1 ps axuww
USER   PID %CPU %MEM   VSZ   RSS  TT  STAT STARTED      TIME COMMAND
root  8264  0.0  0.0  6924   972  ??  SsJ   2:11PM   0:00.00 /usr/sbin/syslogd -ss
root  8395  0.0  0.0  7980  1156  ??  SsJ   2:11PM   0:00.00 /usr/sbin/cron -s
root  8991  0.0  0.1 47400  6628  ??  SsJ   2:16PM   0:00.08 php-fpm: master process (/usr/pbi/minidlna-amd64/php-fpm.conf) (php-fpm)
www   8992  0.0  0.1 49448 10692  ??  IJ    2:16PM   0:00.64 php-fpm: pool www (php-fpm)
www   8993  0.0  0.1 49448 10552  ??  IJ    2:16PM   0:00.11 php-fpm: pool www (php-fpm)
root  9298  0.0  0.0  8048  1048   0  R+J   2:21PM   0:00.00 ps axuww

Code:
[root@freenas] ~# jexec 1 sockstat -4
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
www      php-fpm    8993  0  tcp4   192.168.11.101:12346  *:*
www      php-fpm    8992  0  tcp4   192.168.11.101:12346  *:*
root     php-fpm    8991  10 tcp4   192.168.11.101:12346  *:*
[root@freenas] ~#
 

AlunS

Cadet
Joined
Jun 26, 2012
Messages
9
Just to say I saw a reply to another thread where William suggested using the IP address instead of the host name to access the WebUI, and it appears to have worked!!
 

William Grzybowski

Wizard
iXsystems
Joined
May 27, 2011
Messages
1,754
I'm having similar problems, except without the intermediate step of minidlna working temporarily - it simply wont start at all. Installs fine, no errors in the UI, but fails to add an item to the "Services" tree and gives "some error occured" when attempting to start.

This is an x64 upgrade straight from 8.0.2 (so far, sucessful), so no prior plugin experience. The jail is up and running fine, and responds to pings quite happily. Hardware is an HP NL36, 8GB.

ifconfig -a:

Code:
bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=c0099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO,LINK STATE>
        ether 68:b5:99:72:cc:71
        inet 192.168.178.31 netmask 0xffffff00 broadcast 192.168.178.255
        inet6 fe80::6ab5:99ff:fe72:cc71%bge0 prefixlen 64 scopeid 0x1
        inet6 2001:44b8:513a:7600:6ab5:99ff:fe72:cc71 prefixlen 64 autoconf
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
        media: Ethernet autoselect (100baseTX <full-duplex,flowcontrol,rxpause,txpause>)
        status: active
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 0x2
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 96:10:e7:1e:cc:c2
        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: bge0 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 4 priority 128 path cost 2000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:0b:55:00:04:0a
        inet6 fe80::b:55ff:fe00:40a%epair0a prefixlen 64 scopeid 0x4
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active


jexec 4 ifconfig -a:

Code:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:0b:55:00:05:0b
        inet 192.168.178.201 netmask 0xffffff00 broadcast 192.168.178.255
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>



jexec 4 ps axuww:

Code:
USER   PID %CPU %MEM   VSZ   RSS  TT  STAT STARTED      TIME COMMAND
root  9120  0.0  0.0  5404   988  ??  SsJ  10:11AM   0:00.02 /usr/sbin/syslogd -ss
root  9252  0.0  0.0  5432  1140  ??  IsJ  10:11AM   0:00.03 /usr/sbin/cron -s
root 13433  0.0  0.0  5484   892   1  R+J  12:53PM   0:00.00 ps axuww


jexec 4 sockstat -4:
Code:
sockstat: struct xinpgen size mismatch

Seems like you have installed x86 jail in a x64 freenas or vice-versa...
Delete the jail and start from scratch
 

srhowl

Cadet
Joined
Jul 19, 2012
Messages
3
There seems to be a common theme because I'm also having problems with 8.2 RC1 on a HP Proliant N36L (running the latest firmware). Using an IE9 browser on Windows 7.

I've repeatedly tried reinstalling from scratch and run into the same problems each time. The jail seems to install just fine. If I try to install firefly and minidlna, they seem to install correctly but the icons don't appear in the left hand pane unless I reboot the server. Then I can configure them.
However after configuration Firefly completely refuses to switch to service state=ON, reports "Firefly did not validate please configure it first". Don't know if it's relevant but the Firefly configuration screen also fails to list all the available volumes.

Minidlna will configure and afterwards will "sometimes" switch service state but often won't. If I reboot the server the service state comes up randomly showing ON or OFF and yet the process listing shows minidlna is running. Doesn't appear as though minidlna is communicating properly to other devices even then.

I've also noticed several occasions where I've deleted the jail completely and yet the process listing shows minidlna as running.

Tried the Transmssion module with similar results to minidlna.
 

blade5502

Cadet
Joined
May 2, 2012
Messages
9
Same problem here (clean install, 8.2 RC1, X64)

Jail & Plugin install fine. No configuration tabs in the list for the plugins. According to the wiki the FreeNas box should can ping the Jail IP that this entries show up in the sidebar. I can ping the Jail IP from every host in the Network except the FreeNAS Box (Jail -> FreeNAS = doesn't work; FreeNAS -> Jail =doesn't work; all other hosts can ping both adresses).

Netzwork config:
2 * 1 Gbit NIC -> LACP (lagg0)
3 VLANs
Jail IP is on the same VLAN/Subnet as the Systems default Gateway
 

William Grzybowski

Wizard
iXsystems
Joined
May 27, 2011
Messages
1,754
Please paste:

# ifconfig -a
# jexec 1 ifconfig -a
# jexec 1 ps axuww
# jexec 1 sockstat -4

If you can jump in irc.freenode.net #freenas .
 

Spocksbeer

Cadet
Joined
Jun 6, 2011
Messages
6
Ah, well I sorted my problem. Basically a giant ID10T error on my part - had managed to grab the x86 version of the PBI installer. Didn't notice until after I'd done a factory reset of freenas and went to reinstall it. Doh!

MiniDLNA now humming along fine.

Perhaps 8.2 release should include some idiot proofing in the UI? Or perhaps the idiots should just stay away :p
 
Status
Not open for further replies.
Top