Cannot start most plug-ins... Help!

Status
Not open for further replies.

joshmxpx

Dabbler
Joined
Apr 12, 2014
Messages
14
I have been using freenas for over a year with no issues using jreuhlig's setup.

Today I hit the update button in the sickrage web gui, unsure whether it would work or not.

After the web gui locked out, I rebooted freenas (through the web gui). Now all but one of my plug-ins won't start. I have transmission, couchpotato, sickrage, and Plex installed, but the only one that started upon boot up was transmission.

I tried to start the others through the freenas gui, but none would start. I tried to update the sickrage version through the jail shell, but the plugin wouldn't start after that.

I have no idea where to go from here, I just want to have things back the way they were...

Please give me some pointers on what I can do...

I'm on Freenas 9.10
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Any errors in the logs? What's the output of service plexmediaserver onestart if you run it in the Plex jail.

Sent from my Nexus 5X using Tapatalk
 

joshmxpx

Dabbler
Joined
Apr 12, 2014
Messages
14
Any errors in the logs? What's the output of service plexmediaserver onestart if you run it in the Plex jail.

Sent from my Nexus 5X using Tapatalk

Trying to start plex from the jail ssh shows:

Code:
root@sabnzbd_1:/ # service plexmediaserver onestart
Starting plexmediaserver.


But it doesn't actually start.

Trying to start sickrage from the jail shows:

Code:
root@sabnzbd_1:/ # service sickrage onestart
Starting sickrage.
Traceback (most recent call last):
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/SickBeard.py", line 66, in <module>
	import sickbeard
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/sickbeard/__init__.py", line 43, in <module>
	from sickbeard.indexers import indexer_api
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/sickbeard/indexers/__init__.py", line 21, in <module>
	from . import indexer_api
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/sickbeard/indexers/indexer_api.py", line 26, in <module>
	from indexer_config import indexerConfig, initConfig
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/sickbeard/indexers/indexer_config.py", line 5, in <module>
	from sickbeard import helpers
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/sickbeard/helpers.py", line 57, in <module>
	from sickbeard import classes, db, logger
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/sickbeard/classes.py", line 27, in <module>
	from sickbeard.common import Quality, USER_AGENT
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/sickbeard/common.py", line 35, in <module>
	from fake_useragent import settings as UA_SETTINGS, UserAgent
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/lib/fake_useragent/__init__.py", line 3, in <module>
	from fake_useragent.fake import UserAgent  # noqa
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/lib/fake_useragent/fake.py", line 6, in <module>
	from fake_useragent import settings
  File "/usr/pbi/sickrage-amd64/share/sickrage/SickRage/lib/fake_useragent/settings.py", line 8, in <module>
	DB = os.path.join(tempfile.gettempdir(), 'fake_useragent_{version}.json'.format(  # noqa
  File "/usr/pbi/sickrage-amd64/lib/python2.7/tempfile.py", line 269, in gettempdir
	tempdir = _get_default_tempdir()
  File "/usr/pbi/sickrage-amd64/lib/python2.7/tempfile.py", line 212, in _get_default_tempdir
	("No usable temporary directory found in %s" % dirlist))
IOError: [Errno 2] No usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/']
/usr/local/etc/rc.d/sickrage: WARNING: failed to start sickrage


Viewing the logs, i see this:

Code:
root@sabnzbd_1:/ # less /var/log/messages
Jun 23 04:00:00 sabnzbd_1 newsyslog[37891]: logfile turned over due to size>100K
Jun 23 04:01:00 sabnzbd_1 adjkerntz[37951]: sysctl(set: "machdep.adjkerntz"): Operation not permitted
Jun 23 04:01:00 sabnzbd_1 sendmail[37952]: v5N810Iu037952: SYSERR(root): collect: Cannot write ./dfv5N810Iu037952 (bfcommit, uid=25, gid=25): Permission denied
Jun 23 04:01:00 sabnzbd_1 sendmail[37952]: v5N810Iu037952: SYSERR(root): queueup: cannot create queue file ./qfv5N810Iu037952, euid=25, fd=-1, fp=0x0: Permission denied
Jun 23 04:31:00 sabnzbd_1 adjkerntz[38849]: sysctl(set: "machdep.adjkerntz"): Operation not permitted
Jun 23 04:31:00 sabnzbd_1 sendmail[38850]: v5N8V06W038850: SYSERR(root): collect: Cannot write ./dfv5N8V06W038850 (bfcommit, uid=25, gid=25): Permission denied
Jun 23 04:31:00 sabnzbd_1 sendmail[38850]: v5N8V06W038850: SYSERR(root): queueup: cannot create queue file ./qfv5N8V06W038850, euid=25, fd=-1, fp=0x0: Permission denied
Jun 23 05:01:00 sabnzbd_1 adjkerntz[39774]: sysctl(set: "machdep.adjkerntz"): Operation not permitted
Jun 23 05:01:00 sabnzbd_1 sendmail[39775]: v5N910uA039775: SYSERR(root): collect: Cannot write ./dfv5N910uA039775 (bfcommit, uid=25, gid=25): Permission denied
Jun 23 05:01:00 sabnzbd_1 sendmail[39775]: v5N910uA039775: SYSERR(root): queueup: cannot create queue file ./qfv5N910uA039775, euid=25, fd=-1, fp=0x0: Permission denied
Jun 23 05:31:00 sabnzbd_1 adjkerntz[40688]: sysctl(set: "machdep.adjkerntz"): Operation not permitted
Jun 23 05:31:00 sabnzbd_1 sendmail[40690]: v5N9V0Sm040690: SYSERR(root): collect: Cannot write ./dfv5N9V0Sm040690 (bfcommit, uid=25, gid=25): Permission denied
Jun 23 05:31:00 sabnzbd_1 sendmail[40690]: v5N9V0Sm040690: SYSERR(root): queueup: cannot create queue file ./qfv5N9V0Sm040690, euid=25, fd=-1, fp=0x0: Permission denied
Jun 23 07:13:57 sabnzbd_1 root: /usr/local/etc/rc.d/sickrage: WARNING: failed to start sickrage


Again, any help would be extremely appreciated... I would like to be able to get back up and running without having to lose anything or have to do a fresh reinstall...
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
Did you change the permissions of your jails dataset? Also what is your hardware configuration?
 

joshmxpx

Dabbler
Joined
Apr 12, 2014
Messages
14
Did you change the permissions of your jails dataset? Also what is your hardware configuration?

I did not change any permissions, but I was looking at them, since the only clue initially that something was wrong was that sickrage was giving me permission errors when i tried to rename some files. Before yesterday, though, everything had been working fine for over a year with no issues or errors...

FreeNAS 9.10 STABLE
AMD FX 4300 Quad Core
8GB RAM
WD 3TB, WD 1TB, Seagate 3TB
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
I did not change any permissions, but I was looking at them, since the only clue initially that something was wrong was that sickrage was giving me permission errors when i tried to rename some files. Before yesterday, though, everything had been working fine for over a year with no issues or errors...

FreeNAS 9.10 STABLE
AMD FX 4300 Quad Core
8GB RAM
WD 3TB, WD 1TB, Seagate 3TB
Most people hose their jails by modifying the permissions of the root of the pool or their jail dataset. This doesn't look exactly like that but still could be. I would suggest just rebuilding them because this is not a normal problem and unless you know what you did to cause this it's going to be really hard to figure out how to fix it.

Sent from my Nexus 5X using Tapatalk
 

joshmxpx

Dabbler
Joined
Apr 12, 2014
Messages
14
Most people hose their jails by modifying the permissions of the root of the pool or their jail dataset. This doesn't look exactly like that but still could be. I would suggest just rebuilding them because this is not a normal problem and unless you know what you did to cause this it's going to be really hard to figure out how to fix it.

Sent from my Nexus 5X using Tapatalk

Thanks for this. When you say "rebuild them", do you mean rebuilding the jails? All my plug ins run from the same single jail. What would be the best process to do this? Delete the plug ins and reinstall them? As I said, I'm a bit of a noob with any advanced level stuff in freenas, just follow the tutorials mostly...

Thanks again in advance
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
You're running a lot of plugins and jails for 8GB of RAM.

This:
All my plug ins run from the same single jail.
Does not correlate with this:
I'm a bit of a noob with any advanced level stuff in freenas,

If you are indeed running all plugins in one jail then how did you install them all?
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Thanks for this. When you say "rebuild them", do you mean rebuilding the jails? All my plug ins run from the same single jail. What would be the best process to do this? Delete the plug ins and reinstall them? As I said, I'm a bit of a noob with any advanced level stuff in freenas, just follow the tutorials mostly...

Thanks again in advance

Yes by rebuild I mean create new ones from scratch then copy the configuration over to the new jails. Don't delete the old ones until everything is working again.
You're running a lot of plugins and jails for 8GB of RAM.

This:

Does not correlate with this:


If you are indeed running all plugins in one jail then how did you install them all?
This is the second person this week I found that has done this. What they do is download the plugin from the repo then use the upload template or plugin button in the GUI. This let's you upload them all to the same jail. You get all the plugin ui features and a single jail. It has it's benefits and disadvantages.

Sent from my Nexus 5X using Tapatalk
 
Status
Not open for further replies.
Top