plugin won't restart freenas 9.2.1.5

[n257jy]

ran into an issue where after rebooting Freenas after update to 9.2.1.5 the sabnzbd plugin wouldn't start up. Other plugins plex, sickbeard, couchpotato, start just fine.
if I use the GUI "plugins/installed" restart switch I get the error "Some error has occurred" not really helpful.

Went to jails tab in GUI and stopped / restarted sabnzbd jail. Got this error:
"warden_exception('route: writing to routing socket: File exists\nShared object "libintl.so.9" not found, required by "python2.7\n',)

Have no idea what that is trying to tell me..
Any help wold be greatly appreciated! :)

Edit:
Just found a similar post leading to this bug
https://bugs.freenas.org/issues/3992
Looks like this might be addressed in 9.2.2.*

Any suggestions on how to fix without going to 9.2.2?

 

[dlavigne]

It wouldn't hurt to add a comment to that ticket, indicating that it is still an issue in 9.2.1.5 and asking if there is a work-around for it.

 

[n257jy]

It wouldn't hurt to add a comment to that ticket, indicating that it is still an issue in 9.2.1.5 and asking if there is a work-around for it.

Good point will do...

 

[seer_tenedos]

I am having the same issue on a new install. Everything works till I reboot. Once I reboot only Plex plugin seems to start.

Anyone know the last working version? I need to get this freenas install done in the next few days as the server is going to a different state and I will not have easy access to it.

I assume no one has a work around yet?

Sent from my Nexus 5 using Tapatalk

 

[Stephen Taylor]

I am having a similar problem where my plug-ins are failing to start after upgrading to FreeNAS-9.2.1.5-RELEASE-x64 (80c1d35.

I had a similar issue in FreeNAS-9.2.1.0 and found upgrading to FreeNAS-9.2.1.3 resolved the issue for a few weeks. Now I have upgraded again the issue has re-occurred.

Looking forward to a workaround or solution to this issue as it is driving me nuts-o

 

[TremorAcePV]

I am having a similar problem where my plug-ins are failing to start after upgrading to FreeNAS-9.2.1.5-RELEASE-x64 (80c1d35.

I had a similar issue in FreeNAS-9.2.1.0 and found upgrading to FreeNAS-9.2.1.3 resolved the issue for a few weeks. Now I have upgraded again the issue has re-occurred.

Looking forward to a workaround or solution to this issue as it is driving me nuts-o

This is also my problem.

The first plugin I install always works. If I install more, then reboot, I get issues like yours and the OP's. I'm going to try jumping back to 9.2.1.3 and see if that fixes things.

 

[Stephen Taylor]

I decided to sit, and watch the NAS startup process via the console.
Everything looked to be starting correctly (in my limited knowledge) but when the process got to the jails I noticed it was looking for a file called "LIBINTL.S0.9" (or similar), and was needed by both Python and Python 2.7. The whole thing went quick quickly and I hope I got the file name correct
Once the NAS had started I checked the plugins via the GUI - they existed in the "Plugins" screen, under "Installed" but had totally disappeared from the "plugins" menu, in the left-hand navigation bar.

From what i have managed to glean the plugins are supposed to work flawlessly - when my NAS works with the plugins the system is great - one box to do (nearly) everything makes my life so easy.

Does anyone know when 9.2.1.6 is going to be released ? I noticed the version is in Beta mode, in the nightly builds (hopefully not too far away)

 

[Stephen Taylor]

I have been doing some thinking and, if a plugin specialist or programmer would like to view my environment and issues first-hand, I'd be happy to work with and even grant them access to my NAS.

Please contact me direct if this would be beneficial to the betterment of FreeNAS plugins

 

[TremorAcePV]

I installed 9.2.1.3, did basic network config (DHCP with static IP set from router with a LAGG load balanced between two Ethernet ports), then installed the plugins in this order:

1. Plex Media Server
2. Transmission
3. Sickbeard
4. CouchPotato

I had no issues with installation. However, after installing CouchPotato, I saw this pop up in the console:

Code:

May  6 13:06:24 FREENAS manage.py: [freeadmin.navtree:526] Couldn't retrieve http://10.0.0.98/plugins/couchpotato/4/_s/treemenu: timed out

Then I tried starting each of the plugins (jails were all running already due to installation) in the same order I installed them. Plex failed to start with this:

Code:

May  6 13:07:37 FREENAS kernel: pid 50625 (Plex Media Server), uid 972: exited on signal 11

Transmission and Sickbeard started fine.

CouchPotato gave this before I tried to start it:

Code:

May  6 13:07:21 FREENAS manage.py: [plugins.utils:92] Couldn't retrieve http://10.0.0.98/plugins/couchpotato/4/_s/status: HTTP Error 504: Gateway Time-out

And failed to start.

I never set the Gateway and as I've said, it's the same one everything else is using.

Just as a test, I rebooted the machine, and only CouchPotato and Plex show up in the sidebar navigation. Sickbeard gives this:

Code:

May  6 13:16:53 FREENAS manage.py: [freeadmin.navtree:526] Couldn't retrieve http://10.0.0.98/plugins/sickbeard/3/_s/treemenu: timed out

Plugins > Installed takes forever to load, and Plex is running while the others (all 4 of them show up) are off.

Attempting to start them lets CouchPotato start, but Transmission and Sickbeard sit there and never start and give the Gateway 504 issue that CouchPotato had before.

If I try and click the console after attempting to start Transmission and Sickbeard, it just says "Loading" in green and never loads.

I'll try 9.2.1.1 next. I know I had these plugins all working at one point or another.

 

[Steven Scott]

I am having the same error, only in CouchPotato after a reboot. I am on the latest version at this time, the 9.2.1.7 build. The error occurred and has stopped CouchPotato from loading, but Sickbeard, Plex Media Server, SabNZBd, Headphones and LazyLibrarian are all fine.