Plugins issues

[TrentCL]

1) I cannot delete plugins that were transfered from 9.2. When I search the filesystem, I can see directories that may have been jails for them, but I'm not sure. The error I get when I attempt to delete is: "Error: jail not found". No, the jail is not there, in the directory that was created for jails upon 9.3 upgrade

2) New plugins will not run. Error message: "some errors have occurred. I tried deleting the old plugins during troubleshooting, but I ran into the above issue. I entered plugin jail shell, and discovered that the network adapter was not getting a dhcp address. Not sure if that's because the plugin is service status "off" and cannot turn on without error.

Below are some messages in messages log file that could be relevant, I'm not sure.


Nov 14 10:44:47 freenas bridge0: Ethernet address: 02:3c:03:9b:15:00
Nov 14 10:44:47 freenas kernel: bridge0: link state changed to UP
Nov 14 10:44:47 freenas kernel: bridge0: link state changed to UP
Nov 14 10:44:47 freenas kernel: vmx3f0: promiscuous mode enabled
Nov 14 10:44:47 freenas epair0a: Ethernet address: 02:32:e4:00:05:0a
Nov 14 10:44:47 freenas epair0b: Ethernet address: 02:32:e4:00:06:0b
Nov 14 10:44:47 freenas kernel: epair0a: link state changed to UP
Nov 14 10:44:47 freenas kernel: epair0a: link state changed to UP
Nov 14 10:44:47 freenas kernel: epair0b: link state changed to UP
Nov 14 10:44:47 freenas kernel: epair0b: link state changed to UP
Nov 14 10:44:47 freenas vmx3f0: Capabilities : sg jf vlan
Nov 14 10:44:47 freenas kernel: epair0a: promiscuous mode enabled
Nov 14 10:44:47 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Nov 14 10:44:47 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Nov 14 10:45:56 freenas manage.py: [freeadmin.navtree:544] Couldn't retrieve http://10.1.1.3:5000/plugins/bacula-sd/5/_s/treemenu: HTTP Error 400: Bad Request
Nov 14 10:49:10 freenas kernel: epair0a: link state changed to DOWN
Nov 14 10:49:10 freenas kernel: epair0a: link state changed to DOWN
Nov 14 10:49:10 freenas kernel: epair0b: link state changed to DOWN
Nov 14 10:49:10 freenas kernel: epair0b: link state changed to DOWN
Nov 14 10:49:10 freenas vmx3f0: Capabilities : sg jf vlan csum tso
Nov 14 10:49:10 freenas kernel: bridge0: link state changed to DOWN
Nov 14 10:49:10 freenas kernel: bridge0: link state changed to DOWN
Nov 14 10:49:10 freenas kernel: vmx3f0: promiscuous mode disabled
Nov 14 10:49:13 freenas kernel: ifa_del_loopback_route: deletion failed
Nov 14 10:49:13 freenas Freed UMA keg (udp_inpcb) was not empty (10 items). Lost 1 pages of memory.
Nov 14 10:49:13 freenas Freed UMA keg (udpcb) was not empty (168 items). Lost 1 pages of memory.
Nov 14 10:49:13 freenas Freed UMA keg (tcp_inpcb) was not empty (10 items). Lost 1 pages of memory.
Nov 14 10:49:13 freenas Freed UMA keg (tcpcb) was not empty (4 items). Lost 1 pages of memory.
Nov 14 10:49:13 freenas Freed UMA keg (ripcb) was not empty (10 items). Lost 1 pages of memory.
Nov 14 10:49:13 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Nov 14 10:49:13 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
Nov 14 10:49:23 freenas notifier: Performing sanity check on nginx configuration:
Nov 14 10:49:23 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Nov 14 10:49:23 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Nov 14 10:49:23 freenas bridge0: Ethernet address: 02:3c:03:9b:15:00
Nov 14 10:49:23 freenas kernel: bridge0: link state changed to UP
Nov 14 10:49:23 freenas kernel: bridge0: link state changed to UP
Nov 14 10:49:23 freenas kernel: vmx3f0: promiscuous mode enabled
Nov 14 10:49:23 freenas epair0a: Ethernet address: 02:36:ee:00:05:0a
Nov 14 10:49:23 freenas epair0b: Ethernet address: 02:36:ee:00:06:0b
Nov 14 10:49:23 freenas kernel: epair0a: link state changed to UP
Nov 14 10:49:23 freenas kernel: epair0a: link state changed to UP
Nov 14 10:49:23 freenas kernel: epair0b: link state changed to UP
Nov 14 10:49:23 freenas kernel: epair0b: link state changed to UP
Nov 14 10:49:23 freenas vmx3f0: Capabilities : sg jf vlan
Nov 14 10:49:23 freenas kernel: epair0a: promiscuous mode enabled
Nov 14 10:49:23 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Nov 14 10:49:23 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Nov 14 10:50:33 freenas manage.py: [freeadmin.navtree:544] Couldn't retrieve http://10.1.1.3:5000/plugins/bacula-sd/5/_s/treemenu: HTTP Error 400: Bad Request
Nov 14 11:00:00 freenas syslog-ng[1647]: Configuration reload request received, reloading configuration;
Nov 14 11:06:52 freenas manage.py: [plugins.utils:92] Couldn't retrieve http://10.1.1.3:5000/plugins/bacula-sd/5/_s/status: HTTP Error 400: Bad Request



9.2 plugins that do not work after upgrade and cannot be deleted: xdm, subsonic
9.3 plugins installed but give errors: syncthing, bacula-sd

 

[Bill Lightstone]

Hi There,

Yes similar issue, Installed minidlna from the list of plugins, I can get the jail running but when I go to start the plugin under plugins/installed it just wont switch on. I did a very quick trial with plexmediaserver and had the same issue. It seems that plugin's wont start on my system

 

[sdspieg]

The plugins I had from the previous version did make the move quite graciously - with the single exception of minidlna, which indeed I cannot turn on. Also the GUI-based plugin update - of at least subsonic and sabnzbd - also worked for me now, which they had never done before. I'm still reluctant to try to update PMS that way, as if that doesn't work properly, it is a LOT of work to restore everything.

 

[sdspieg]

I CAN report, however, that I can no longer see the menu under 'plugins' in the left pane, the way I could in previous versions. Which means I can't double-check the exact URL that gives access to the plugin. So for instance, I was able to install syncthing through the GUI, and it does turn on, I obviously know the jail's IP, but still I do not seem to be able to get into the URL that gives access to the synthing webgui.

 

[dj542]

I have the same issue with the plugins tree in the left pane. Depending on which jails are running I'll see different plugins in the tree, if all jails are running I won't see any plugins. Crashplan refuses to run when other plugins are running.

 

[BigJ]

Hi

IIRC there was a bug report that mentioned having to access the WebUI using http to correctly see the Plugin tree, not https.

 

[churnd]

I'm having some issues as well. Mine is a fresh install of 9.3 Beta. The available plugins list is a little slow to pull up. I can install them & their respective jails are reachable on the network, but I can't turn them on. Here's the logs:

Code:

Nov 28 05:26:41 FreeNAS manage.py: [freeadmin.navtree:544] Couldn't retrieve http://192.168.1.30/plugins/transmission/1/_s/treemenu: timed out
Nov 28 05:26:41 FreeNAS manage.py: [freeadmin.navtree:544] Couldn't retrieve http://192.168.1.30/plugins/crashplan/2/_s/treemenu: timed out
Nov 28 05:26:46 FreeNAS manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.1.30/plugins/transmission/1/_s/status: No JSON object could be decoded
Nov 28 05:26:46 FreeNAS manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.1.30/plugins/crashplan/2/_s/status: No JSON object could be decoded
Nov 28 05:32:37 FreeNAS manage.py: [freeadmin.navtree:544] Couldn't retrieve http://192.168.1.30/plugins/transmission/1/_s/treemenu: timed out
Nov 28 05:32:37 FreeNAS manage.py: [freeadmin.navtree:544] Couldn't retrieve http://192.168.1.30/plugins/crashplan/2/_s/treemenu: timed out
Nov 28 05:33:41 FreeNAS manage.py: [freeadmin.navtree:544] Couldn't retrieve http://192.168.1.30/plugins/transmission/1/_s/treemenu: timed out
Nov 28 05:33:41 FreeNAS manage.py: [freeadmin.navtree:544] Couldn't retrieve http://192.168.1.30/plugins/crashplan/2/_s/treemenu: timed out
Nov 28 05:34:47 FreeNAS manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.1.30/plugins/crashplan/2/_s/status: No JSON object could be decoded
Nov 28 05:34:47 FreeNAS manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.1.30/plugins/transmission/1/_s/status: No JSON object could be decoded

 

[BigJ]

Hi churnd

Are you connecting to the WebGUI using https? There is (was) a know bug with the this that means the plugins could only be properly controlled when the WebGUI is accessed using http.

 

[churnd]

Hi churnd

Are you connecting to the WebGUI using https? There is (was) a know bug with the this that means the plugins could only be properly controlled when the WebGUI is accessed using http.

Hi BigJ,

No, just using HTTP.

 

[BigJ]

It's a bit heavy handed (I'm relatively new to FreeNAS) but you could try restarting the plugin system.

service ix-plugins restart

 

[churnd]

It's a bit heavy handed (I'm relatively new to FreeNAS) but you could try restarting the plugin system.

service ix-plugins restart

I've restarted the NAS a few times, & no joy there either. I guess it's another bug?

 

[BigJ]

Hopefully someone with a better handle on working with plugins can help. One last suggestion if I may. Have you tried starting the plugin service from the CLI? It's the only way I found to get minidlna going (it's a know problem with the plugin). Open a shell from the jail, not the host system, and try

service name-of-plugin start
OR
service name-of-plugin onestart

 

[churnd]

Hopefully someone with a better handle on working with plugins can help. One last suggestion if I may. Have you tried starting the plugin service from the CLI? It's the only way I found to get minidlna going (it's a know problem with the plugin). Open a shell from the jail, not the host system, and try

service name-of-plugin start
OR
service name-of-plugin onestart

Ah, yep, starting from CLI works great! I guess the plugins need to be updated for 9.3?

 

[BigJ]

Step in the right direction :) I'm not sure it's a problem with the plugins as transmission will start successfully for me from the WebGUI. I'd guess that something isn't quite right on you system but I'm not sure what else to suggestion at this point.

 

[BigJ]

Something just occurred to me. The bug report I mentioned earlier stated that the 'Protocol' configuration had to be set to 'HTTP' for the plugins to be controllable, 'HTTP+HTTPS' failed. It's a long shot, check System->General->Protocol option.

 

[churnd]

Something just occurred to me. The bug report I mentioned earlier stated that the 'Protocol' configuration had to be set to 'HTTP' for the plugins to be controllable, 'HTTP+HTTPS' failed. It's a long shot, check System->General->Protocol option.

Yeah, that's set to just HTTP.