plugins don't work anymore

[Rob1]

Hi,

I have on my FreeNAS 9.1.1. the Plex and Owncloud plugins installed. They both worked fine, untill yesterday! Yesterday I had to work on the electricity on my hous. So I shut down the FreeNAS and turned off the electricity. After work was don I restarted the FreeNAS and now the plugins don't work anymore.

How come? And what to do? Reinstall the plugins?

I reboot the system today for one time, but no results.

 

[ijfrederick]

I have a similar issue but I have isolated the source to deleting an unwanted plugin. I have been able to duplicate this issue: I installed a plugin, then I deleted it and it broke one that was already working. Seems that for some reason the PHP-FPM is gone from the plugin. Everything else in the jail works, however, the FreeNAS UI is now unable to communicate with the plugin. In addition I did an NMAP scan and the jail is not listening on the 123xx port used for fastCGI. Anyone out there have any ideas?

 

[Rob1]

No body?

I deleted te plugins and reinstalled Plex plugin. That doesn't help.
Do I have ro reinstall freeNAS compleetly to get all working again?

 

[cyberjock]

You shouldn't have to reinstall FreeNAS again. But so many people don't understand the plugin system that people like me that do know what we are doing just close the browser on threads like this. We get them so frequently I really don't like getting involved with them anymore. Last time I helped someone with a plugin I spent almost 10 hours with them on Skype/Teamviewer. Since I'm an unpaid volunteer its really not worth my time. Most of the other experienced users are the same way.

 

[Rob1]

@cyberjock, I understand. And you don't have to help me with my plugins. I will just reinstall FreeNAS, it's not to much work. I just have one question; do you know what's the cause of issue? My be there's a way to avoid it next time I have to restart for some reason.

 

[cyberjock]

Nope. If I did I would have told you how to fix it.

 

[marcevan]

Problem is due to jails both being datasets in your pool and being associated with plugins.

You can have multiple jails and you can have multiple versions of plugins within a single jail or spread out.

When you delete a jail it does not delete the plugin, unfortunately, so you have orphaned plugins.

That's the genesis of the issue.

I have seen nothing showing where the plugin to jail linkages are actually stored (in db? in file?) that would help.

 

[ijfrederick]

As far as I can tell, the connection between the Jail, the plugin and the GUI are accomplished using PHP-FPM and in my case, for some reason, when I delete an unwanted plugin, it affects the FPM on another plugin. I cannot tell if it is the last plug in to be installed before it. So when the GUI tries to communicate with the plugin using a HTTP port on the jail, since FPM is non-existent, I get this message: "... HTTP Error 502: Bad Gateway"

 

[dlavigne]

That sounds like a bug. Please create a bug report at bugs.freenas.org and post the issue # here.

 

[marcevan]

I don't necessarily know if it's a bug: I think it's lack of information.

If there's a core file that houses the linkage that would let us fix it and at least post a bug of insight.

If it's in the database, then I don't think we know the way to log in and fix a table without having db, user, pass, etc.

Basically, I'm asking for more information before posting a bug.

 

[marcevan]

Update:

sqlite3 /data/freenas-v1.db \ "select * from services_pluginsjail"

mine is empty, but even if I add a new plugin it's not populated so not sure if 9.2.0 is using this table at all; however:

if you sqlite3 and do a .schema services_pluginsjail you get the create statement for the table:

Code:

jail_path varchar(255) NOT NULL,
plugins_path varchar(255) NOT NULL,
jail_mac varchar(17) NOT NULL,
jail_ipv4address varchar(42) NOT NULL,
jail_name varchar(120) NOT NULL,
jail_ipv4netmask varchar(3) NOT NULL,
id integer, NOT NULL

Since I added the DLNA plugin successfully and see it in my navtree but it's not in this table, I'm pretty sure it's a red herring.

If however there is another table storing the linkage now (e.g., not a services_* table) we should be well on our way.