sabnzbd / sickbeard / couchpotato pbi's

Status
Not open for further replies.

calgarychris

Contributor
Joined
Aug 27, 2011
Messages
124
Toddos, thanks for the grep suggestion - when I type that in, it doesn't display anything onscreen.

Just an FYI for Joshua, I don't think it's a big deal, but I think that the log file is probably picking up whatever you've got on your system. My log file is 9MB (I've only just installed SB) and contains records (post processing) for shows I've never even heard of. Not sure that you care, but it might be an idea to delete it or delete the content (and it'll save 9MB from your pbi presumably!).

I'll try to chmod the directory again to see if that does anything.

Thanks
Chris
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
Toddos, thanks for the grep suggestion - when I type that in, it doesn't display anything onscreen.

Just an FYI for Joshua, I don't think it's a big deal, but I think that the log file is probably picking up whatever you've got on your system. My log file is 9MB (I've only just installed SB) and contains records (post processing) for shows I've never even heard of. Not sure that you care, but it might be an idea to delete it or delete the content (and it'll save 9MB from your pbi presumably!).

I'll try to chmod the directory again to see if that does anything.

Thanks
Chris

I have no idea what you are talking about. I develop these plugins on an ubuntu machine. and build them on a clean freenas jail. Neither have and of these programs running. I don't know why your saying something I'm doing is getting into your logs?
Your logs are 9MBs? The log directory isn't even created till Sickbeard is started so i don't think it can save space from the plugins...
Sorry, just confused what your are saying I need to do?
 

toddos

Contributor
Joined
Aug 18, 2012
Messages
178
Toddos, thanks for the grep suggestion - when I type that in, it doesn't display anything onscreen.

Just an FYI for Joshua, I don't think it's a big deal, but I think that the log file is probably picking up whatever you've got on your system. My log file is 9MB (I've only just installed SB) and contains records (post processing) for shows I've never even heard of. Not sure that you care, but it might be an idea to delete it or delete the content (and it'll save 9MB from your pbi presumably!).

I'll try to chmod the directory again to see if that does anything.

Thanks
Chris

Set the completed download permissions in Sab's config as well as chmodding. The plugins are setup with their own user:group and don't share groups. By default, Sab's download directory isn't going to be accessible to sickbeard (or couchpotato or headphones). You can change the services to all run as the same user (and chown everything appropriately) but I wouldn't recommend it. If you change Sab to set completed downloads to 777, everything can access them.

It'd probably be nice if the plugins all used a shared group as mentioned elsewhere, but you still may want to make things read/writeable to all for various reasons.
 

calgarychris

Contributor
Joined
Aug 27, 2011
Messages
124
Fixed - I chmodded it again and that seemed to fix the problem..weird.

Joshua - sorry I didn't mean to insult you or anything, please don't take it as that...I just opened a really big log file on a jail I just created and installed the pbis on and assumed it was somehow picking up something...Anyway, it's no big deal, I'll just delete it.
 

Mtc

Cadet
Joined
Sep 1, 2012
Messages
2
Problem getting sickbeard started

First up, thanks for all the great work getting this up and running.

I'm having difficulties getting sickbeard started. Ive installed the plugin but the switch on the freenas control panel is 'off' and i cant seem to start it. All your other 0.8 plugins work perfectly.

Any suggestions?
 

sdspieg

Contributor
Joined
Aug 6, 2012
Messages
168
Just installed everything - thanks to the developpers. Everything seems to work properly - except for one (critical) step which I must have overlooked. I mounted /mnt/FreeNAS/Video to /mnt/FreeNAS/jail/software/media, and sabnzbd shows that everything got downloaded properly, I chmodded the folder into which it downloads everything (/software/pbi/sabnzbd-amd64/data/Downloads/complete) to 777 - meaning I now 'see' all downloaded files when I ftp into it for instance. But obviously my server doesn't 'see' the folders as they are in /software/pbi/sabnzbd-amd64/data/Downloads/complete and not in /mnt/FreeNAS/jail/software/media. Is there any way to tell sabnzbs to put the completed files directly into /mnt/FreeNAS/jail/software/media (which, I presume, would then be 'visible' because of the mount point? Or am I missing sthg here?

BTW couldn't the key nuggets from this thread be put into the wiki? Or at least in a sticky here on the forum?

Thanks!

-Stephan
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
Fixed - I chmodded it again and that seemed to fix the problem..weird.

Joshua - sorry I didn't mean to insult you or anything, please don't take it as that...I just opened a really big log file on a jail I just created and installed the pbis on and assumed it was somehow picking up something...Anyway, it's no big deal, I'll just delete it.

Not taken as an insult, I was just confused. Hope you got everything working!
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
First up, thanks for all the great work getting this up and running.

I'm having difficulties getting sickbeard started. Ive installed the plugin but the switch on the freenas control panel is 'off' and i cant seem to start it. All your other 0.8 plugins work perfectly.

Any suggestions?

Sometimes the page needs a refresh cause the pidfile isn't created fast enough and the freenas page shows sabnzbd as off when it's really running. Or if a refresh of the page doesn't show a change try running..
Code:
service sabnzbd start

in your jail and see if any errors come up.
 

toddos

Contributor
Joined
Aug 18, 2012
Messages
178
Just installed everything - thanks to the developpers. Everything seems to work properly - except for one (critical) step which I must have overlooked. I mounted /mnt/FreeNAS/Video to /mnt/FreeNAS/jail/software/media, and sabnzbd shows that everything got downloaded properly, I chmodded the folder into which it downloads everything (/software/pbi/sabnzbd-amd64/data/Downloads/complete) to 777 - meaning I now 'see' all downloaded files when I ftp into it for instance. But obviously my server doesn't 'see' the folders as they are in /software/pbi/sabnzbd-amd64/data/Downloads/complete and not in /mnt/FreeNAS/jail/software/media. Is there any way to tell sabnzbs to put the completed files directly into /mnt/FreeNAS/jail/software/media (which, I presume, would then be 'visible' because of the mount point? Or am I missing sthg here?

BTW couldn't the key nuggets from this thread be put into the wiki? Or at least in a sticky here on the forum?

Thanks!

-Stephan

Yes, you can do exactly that. First, mount your main media storage dataset somewhere inside your jail using the plugin mount points configuration in the FreeNAS UI (Sharing, Plugins, View Mount Points, Add Mount Point). In my example, I have a dataset at /mnt/aux/public" that I mount as "/mnt/public" in my jail. From the jail's perspective, that dataset is now available at /mnt/public and that's what we'll use elsewhere.

In SAB's config (open the SAB web page, click "Config" at the top-left), do the following:

  • Click "Folders" on the left
  • Set the value of "Completed Download Folder" to a folder in your dataset, based on the mount point above. In this example, I'm using "/mnt/public/downloads". chmod that folder to 777 if it's not already.
  • Set the value of "Permissions for completed downloads" to 777
  • If you want to have easy access to incomplete and temporary files, do the same with "Temporary Download Folder". I usually don't change this.
  • If you intend to use the blackhole method of nzb downloading, set "Watched Folder" to a different folder on your mount point. I use "/mnt/public/nzbs". Again, make sure this folder is chmodded to 777.

The key thing to remember is that the jail only sees what's inside the jail. If you don't mount your data sets inside your jail, it can't access them. When you do mount your datasets inside your jail, you need to refer to them from the jail root ("/mnt/public") and not the host root ("/mnt/aux/jail/nasapps/mnt/public", where "/mnt/aux/jail/nasapps" is the dataset where my jail is rooted).
 

russdyer

Dabbler
Joined
Sep 28, 2011
Messages
45
I'm sorry if this has been discussed already...

Added the sabnzbd plugin. Added sabnzbd_enable="YES" to the etc/rc.conf file.

When I type: "service sabnzbd start", I get the following:

Starting sabnzbd.
software# Sorry, requires Python module sqlite3
Try: apt-get install python-pysqlite2

Any advice would be appreciated.

Thanks,
Russ
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
Try: apt-get install python-pysqlite2

Any advice would be appreciated.

Thanks,
Russ

This is what happens when you develop FreeBSD stuff on a Linux system.... there is no "apt-get" in FreeBSD, only Linux, which is what Joshua is trying to create his plugins on...

You're not doing anything wrong, just wait for a fix.
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
Protosd that error has nothing to do with me building anything on linux. I don't build on linux, just edit files on it cause that's what I run on my desktop. I build on a FreeBSD jail. That error is just part of python in FreeBSD, kinda weird it gives you a debian solution to a freebsd version of python but I guess they didn't edit that part of the python source when they compiled it for FreeBSD.

Anyway, Russ what version of the plugin did you install? Try version 0.8.1. And please start/stop stuff from the gui, you shouldn't have to to touch the commandline with version 0.8 and up. Read the OP for the links
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
Hmmm, that is strange, sorry about that then. I just find it good to keep things clean and do everything your developing in the same environment. Sounds like a bug report should be submitted to the port maintainer for that port then.
 

russdyer

Dabbler
Joined
Sep 28, 2011
Messages
45
I can't start any of your plugins from the GUI. I get an "Errors have Occurred" message in the GUI whenever I try to turn on any of the plugins. I've downloaded the latest from your file share. For SABnzbd, it is 0.8.1. I'm on the freenas 8.3 Beta 1 but I'm waiting on the final to update the zpool. Is this the issue? I have updated to the latest jail.
 

Mtc

Cadet
Joined
Sep 1, 2012
Messages
2
Sometimes the page needs a refresh cause the pidfile isn't created fast enough and the freenas page shows sabnzbd as off when it's really running. Or if a refresh of the page doesn't show a change try running..
Code:
service sabnzbd start

in your jail and see if any errors come up.

Thanks. What actually worked was to stop the service and start it again: service sickbeard stop, then service sickbeard start

Not sure why this is, or whether its unique to me, but every time I restart freenas, I can't get sickbeard to start up from the control panel. Running the above fixes the problem and sickbeard then operates as usual.
 

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
Wolfman, 0.8.1 fixes a bug in sabnzbd which toddos pointed out. I didn't include the tbb library. This is needed because I switched to the multithreaded (tbb) version of par in version 0.8.

russ, try starting an official plugin and see if you have an issue. Every once in a while the same happens to me where the FreeNAS gui can't communincate with the plugins. A restart is how I fix it, but that isn't a great answer for a production system...
 

Cattmy

Cadet
Joined
Sep 2, 2012
Messages
2
Is there any way that I can get SickBeard to store TV Shows on another volume?
 

russdyer

Dabbler
Joined
Sep 28, 2011
Messages
45
Thanks everybody for all your help, but I think I found the issue. I restarted, but this didn't have any effect. I removed all plugins and reinstalled the Plugin Jail. Reinstalled plugins and now they successfully turn on in the GUI (except for Headphones). No error message, it just won't turn on.

What port number are used for SABnzbd, SickBeard, Headphones, Couch Potato? Thanks again.

According to the SABnzbd config.ini file, the default HTTPS port number is set to port 9090. But if I go to https://jailip:9090 it doesn't work.
 

toddos

Contributor
Joined
Aug 18, 2012
Messages
178
Thanks everybody for all your help, but I think I found the issue. I restarted, but this didn't have any effect. I removed all plugins and reinstalled the Plugin Jail. Reinstalled plugins and now they successfully turn on in the GUI (except for Headphones). No error message, it just won't turn on.

Is there anything in the message log? You can get the messages log in your UI by going to Server -> Settings -> Advanced and turning on "Show console messages in the footer". That should add a log in the footer of the FreeNAS web page that you can click to expand and watch for errors.

A couple of things to check:
  • Verify headphones isn't running (ps waux | grep headphones). If it's not, delete any /usr/pbi/headphones_`uname -m`/data/headphones.pid file
  • Make sure file ownership for everything under headphones is chowned to headphones:headphones (user and group). If not, chown -R that. I had an issue related to this when I installed the 0.8 pbis (I suspect that was from migrating my data folders back into place, rather than an actual bug in the pbi).

What port number are used for SABnzbd, SickBeard, Headphones, Couch Potato? Thanks again.

According to the SABnzbd config.ini file, the default HTTPS port number is set to port 9090. But if I go to https://jailip:9090 it doesn't work.

SAB's default port = 8080
SickBeard's default port = 8081
CouchPotato Server's default port = 5050
Headphones' default port = 8181

(not 100% sure on these, as I change the ports myself)

Note that SAB is not configured for SSL by default, so although its default SSL port is 9090, it's not listening on that port unless you enable it to do so. That would explain why https://jailip:9090 does't work for you.
 
Status
Not open for further replies.
Top