Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

SABnzbd+ SickBeard CouchPotato Plugin/Installer for v5b11+

Featured Replies

Anyone know how uninstall the pkg manger version?

  • Replies 1.2k
  • Views 252.7k
  • Created
  • Last Reply

In unMenu, just uncheck the install on reboot option. Then go to your SAB GUI and shut it down. Clear the downloaded files out of the packages folder by just browsing to the flash drive if you like.

 

Yes you have control over where it is installed. See the first post for screenshots and install instructions. For the install directory, you can just direct it to the folder where you already have it installed on the cache drive. You can ignore the data directory checkbox then. Adjust your port to match and run as nobody.

 

does cache files go with flash/packages or i have delete that too to stop conflict?

 

Seems i've ran into bit of toruble running sickbeard install as unmenu hangs after i click appli settings:

 

installing latest Version of sickbeard

Starting sickbeard: sudo -u root python /usr/local/sickbeard/SickBeard.py -d -p 8082 --datadir /mnt/cache/.app/sickbeard --pidfile /var/run/sickbeard/sickbeard.pid > /dev/null 2>&1

 

clicked apply and says sickbeard up and running but folder is empty bring up permission issues

I installed the plugin after upgrading from 4.7 to 5.0b14 and got the following messages:

 

root@Tower:~# installplg /boot/config/plugins/sabnzbd-0.4c-i468-bw.plg

installing plugin: sabnzbd-0.4c-i468-bw

file /boot/packages/python-2.6.4-i486-1.txz: already exists

  upgradepkg --install-new /boot/packages/python-2.6.4-i486-1.txz ...

+==============================================================================

| Skipping package python-2.6.4-i486-1 (already installed)

+==============================================================================

 

 

success

file /boot/packages/python-cheetah-2.4.2.1-i486-1alien.tgz: already exists

  upgradepkg --install-new /boot/packages/python-cheetah-2.4.2.1-i486-1alien.tgz ...

+==============================================================================

| Skipping package python-cheetah-2.4.2.1-i486-1alien (already installed)

+==============================================================================

 

 

success

file /boot/packages/python-yenc-0.3-i486-1alien.tgz: already exists

  upgradepkg --install-new /boot/packages/python-yenc-0.3-i486-1alien.tgz ...

+==============================================================================

| Skipping package python-yenc-0.3-i486-1alien (already installed)

+==============================================================================

 

 

success

file /boot/packages/sqlite-3.6.23.1-i486-1.txz: already exists

  upgradepkg --install-new /boot/packages/sqlite-3.6.23.1-i486-1.txz ...

+==============================================================================

| Skipping package sqlite-3.6.23.1-i486-1 (already installed)

+==============================================================================

 

 

success

file /boot/packages/unrar-3.9.10-i486-2alien.tgz: already exists

  upgradepkg --install-new /boot/packages/unrar-3.9.10-i486-2alien.tgz ...

+==============================================================================

| Skipping package unrar-3.9.10-i486-2alien (already installed)

+==============================================================================

 

 

success

file /boot/packages/infozip-5.52-i486-2.tgz: already exists

  upgradepkg --install-new /boot/packages/infozip-5.52-i486-2.tgz ...

+==============================================================================

| Skipping package infozip-5.52-i486-2 (already installed)

+==============================================================================

 

 

success

file /boot/packages/openssl-0.9.8n-i486-1.txz: already exists

  upgradepkg --install-new /boot/packages/openssl-0.9.8n-i486-1.txz ...

+==============================================================================

| Skipping package openssl-0.9.8n-i486-1 (already installed)

+==============================================================================

 

 

success

file /boot/packages/pyopenssl-0.10-i486-2sl.txz: already exists

  upgradepkg --install-new /boot/packages/pyopenssl-0.10-i486-2sl.txz ...

+==============================================================================

| Skipping package pyopenssl-0.10-i486-2sl (already installed)

+==============================================================================

 

 

success

file /boot/packages/par2cmdline_tbb-0.4-i486-1kh.tgz: already exists

  upgradepkg --install-new /boot/packages/par2cmdline_tbb-0.4-i486-1kh.tgz ...

+==============================================================================

| Skipping package par2cmdline_tbb-0.4-i486-1kh (already installed)

+==============================================================================

 

 

success

file /boot/config/plugins/sabnzbd/sabnzbd.png: downloading from http://unraid.benjaminwaller.de/sabnzbd/sabnzbd.png ... 2012-01-31 13:14:04 URL:http://unraid.benjaminwaller.de/sabnzbd/sabnzbd.png [5244/5244] -> "/boot/config/plugins/sabnzbd/sabnzbd.png" [1]

success

file /tmp/sabnzbd-cleanup: successfully wrote INLINE file contents

  /bin/bash /tmp/sabnzbd-cleanup ... success

file /boot/config/plugins/sabnzbd/sabnzbd.cfg: successfully wrote INLINE file contents

file /etc/rc.d/rc.sabnzbd: successfully wrote INLINE file contents

  successfully changed file mode

file /usr/local/emhttp/plugins/sabnzbd/sabnzbd.page: successfully wrote INLINE file contents

file /usr/local/emhttp/plugins/sabnzbd/sabnzbd.png: successfully copied LOCAL file

file /usr/local/emhttp/plugins/sabnzbd/sabnzbd.php: successfully wrote INLINE file contents

file /usr/local/emhttp/plugins/sabnzbd/event/disks_mounted: successfully wrote INLINE file contents

  successfully changed file mode

file /usr/local/emhttp/plugins/sabnzbd/event/unmounting_disks: successfully wrote INLINE file contents

  successfully changed file mode

file /tmp/sabnzbd-install: successfully wrote INLINE file contents

  /bin/bash /tmp/sabnzbd-install ... success

file /var/log/plugins/sabnzbd: successfully wrote INLINE file contents

plugin successfully installed

 

I guess there are many leftovers from when I installed the unmenu sabnzb package.  Does everything look good so far?

 

What must be following step?

 

Currently the old SABNZB is still at /mnt/cache/.sabnzb, can it stay there? Or must it be deleted?

 

The attached picture shows up in unraid now.

 

Can I point the Install dir and Data dir to /mnt/cache/.sabnzb?

Set enable sabnzbd to Yes.

I already changed the port to 8085.

Will I also get an option to update to the latest version?

SABnzbd.jpg.5d9b93af99a4afabd65b7b45ba7dde70.jpg

Yes, point the install directory to /mnt/cache/.sabnzb. You can ignore the data directory since they are both going to be the same location. Just leave it unchecked.

I have the plugins installed, just having a bit of SB trouble. I have it installed to the default install directory (RAM I believe) and a data directory on the cache drive. However, this means that my autoProcessTV.cfg gets wiped whenever I reboot the server. Is there a way around this or should I just move the install directory elsewhere?

autoProcessTV.cfg should be in the sickbeard data dir

 

In my case /mnt/usenet/apps/sickbeard/autoProcessTV/autoProcessTV.cfg

 

My settings do not get wiped on reboot

Screenshot_Sickbeard.png.2acacea04235476720aa2e4b30115cbe.png

autoProcessTV.cfg should be in the sickbeard data dir

 

In my case /mnt/usenet/apps/sickbeard/autoProcessTV/autoProcessTV.cfg

 

My settings do not get wiped on reboot

 

Strange, for me the autoProcessTV folder is definitely in the install directory. The only folders I have in the data directory are 'cache' and 'logs', along with the config and database files :S should I manually move the autoprocessTV folder?

Yes, I had to move it and edit as needed if I remember correctly. Will dig for the documentation and repost.

 

I found it: http://code.google.com/p/sickbeard/wiki/PostProcessing

 

It says "To set up post processing, first copy the contents of the autoProcessTV directory from your Sick Beard installation to your SABnzbd+ scripts folder (or set your scripts folder to the location of the autoProcessTV directory). Rename autoProcessTV.cfg.sample to simply autoProcessTV.cfg and open it in a text editor."

 

Now that I re-read that, I'm not sure how I figured out to move it where I did?

Yes, I had to move it and edit as needed if I remember correctly. Will dig for the documentation and repost.

 

If it is supposed to be moved then that's my bad - my first time using the new plugins and didn't want to mess around too much - assumed that everything would already be where it should!

I don't want to break your installation either. Check your SABnzbd config page. It needs to point to your autoProcessTV folder

Screenshot_SABnzbd_Folders.png.cd8dec9208a2178ab55743af1b989386.png

I don't want to break your installation either. Check your SABnzbd config page. It needs to point to your autoProcessTV folder

 

Am trying to get it to do this, but I seem to be having some trouble with the cache drive. I can't write to it all of a sudden, even though I could fine before a reboot, and I also can't point SAB to it! Says it cannot access. The cache also has a 'Music' folder stuck on it that the mover refuses to move. How can a reboot break so many things? :S

 

The cache export setting is set to public, so no clue what is going on :/

I don't want to break your installation either. Check your SABnzbd config page. It needs to point to your autoProcessTV folder

 

Am trying to get it to do this, but I seem to be having some trouble with the cache drive. I can't write to it all of a sudden, even though I could fine before a reboot, and I also can't point SAB to it! Says it cannot access. The cache also has a 'Music' folder stuck on it that the mover refuses to move. How can a reboot break so many things? :S

 

The cache export setting is set to public, so no clue what is going on :/

 

Could be a permissions issue?

 

I don't use a cache drive, I am sure there are others here using a cache drive that can offer some assistance.

It may be time consuming, but I had to re-read this entire thread several times before I got it all working properly.

 

I just found the autoProcessTV references in Benni-chans post on page# 6 of thist hread

I don't want to break your installation either. Check your SABnzbd config page. It needs to point to your autoProcessTV folder

 

Am trying to get it to do this, but I seem to be having some trouble with the cache drive. I can't write to it all of a sudden, even though I could fine before a reboot, and I also can't point SAB to it! Says it cannot access. The cache also has a 'Music' folder stuck on it that the mover refuses to move. How can a reboot break so many things? :S

 

The cache export setting is set to public, so no clue what is going on :/

 

Could be a permissions issue?

 

I don't use a cache drive, I am sure there are others here using a cache drive that can offer some assistance.

It may be time consuming, but I had to re-read this entire thread several times before I got it all working properly.

 

I just found the autoProcessTV references in Benni-chans post on page# 6 of thist hread

 

Yeah these new permissions seem to be doing much more harm than good for a lot of people. It seems the problem is that I copied the autoProcessTV folder as root - that's the only way I know how, using a telnet session! Is there any other way to access /usr/local as a named user rather than root?

Yeah these new permissions seem to be doing much more harm than good for a lot of people. It seems the problem is that I copied the autoProcessTV folder as root - that's the only way I know how, using a telnet session! Is there any other way to access /usr/local as a named user rather than root?

 

I found some more notes  from my installation regarding permissions.

Maybe something here will help.

Just change to paths to suit your needs:

 

"find out who is the owner"

ls -al /mnt/usenet/apps/sabnzbd/

 

"change owner to nobody"

chown -R nobody:users /mnt/usenet/apps/sabnzbd/

 

"check the user rights" (the .py files should have read and execution rights for at least user and group)

ls -la /mnt/usenet/apps/sickbeard/autoProcessTV

 

I just had a 2 hour battle with the sabToSickbeard.py script.  It would not show up in the SabNZBD script dropdown menu.  IT WAS DRIVING ME CRAZY!  I had everything pointing to the right folder.  After some heavy googling, I found out that you had to run this command to make the script visible.

 

"chmod +x sabToSickBeard.py"

 

Would someone explain that to me, please?  Maybe it was obvious to everyone else that it was necessary, but I don't know very much about linux and it was extremely frustrating to dig for that info.

 

Do I have to do another command to make sure it executes every time I boot?

sorry my just be me being retarded but there difference between sabnzbd+ and sabnzbd

 

Also my sabnzb does not have a script folder does everyone just make it themselves?

 

There seems to be issues with sabnzbd hanging after i try to enable it.

Starting sabnzbd: sudo -u nobody python /mnt/cache/.app/sabnzbd//SABnzbd.py -d -s 0.0.0.0:8081 --config-file /usr/local/sabnzbd --pid /var/run/sabnzbd > /dev/null 2>&1

I've tried refreshing but it just put me back to pre-apply state

Well... Me again. Still having the problem with sabnzb's having 0,00GB of space available.

 

I've read the entire thread several times now and followed every guide tip and what not, but still the prob persists.

 

Quick prob. Description:

 

I have a clean install of UnRaid 5.0 b14, Snap mounted 120GB drive shared to /mnt/usenet.

 

Sabnzb, couchpotato, sick beard configured and running well.

 

The problem is that Sabnzb refuses to download because there is no free space available.

 

Tried giving new folders, different shares etc. etc. ....

 

Nothing.

 

This is totally frustrating me, can anybody help me out, PLZ??!?!?

 

Thx I.A.

 

Fuddster

 

Will attach sys log in a sec.

 

I just had a 2 hour battle with the sabToSickbeard.py script.  It would not show up in the SabNZBD script dropdown menu.  IT WAS DRIVING ME CRAZY!  I had everything pointing to the right folder.  After some heavy googling, I found out that you had to run this command to make the script visible.

 

"chmod +x sabToSickBeard.py"

 

Would someone explain that to me, please?  Maybe it was obvious to everyone else that it was necessary, but I don't know very much about linux and it was extremely frustrating to dig for that info.

 

Do I have to do another command to make sure it executes every time I boot?

I think something should be made about this on the first page just aviod confusion same question being asked

I don't want to break your installation either. Check your SABnzbd config page. It needs to point to your autoProcessTV folder

 

Am trying to get it to do this, but I seem to be having some trouble with the cache drive. I can't write to it all of a sudden, even though I could fine before a reboot, and I also can't point SAB to it! Says it cannot access. The cache also has a 'Music' folder stuck on it that the mover refuses to move. How can a reboot break so many things? :S

 

The cache export setting is set to public, so no clue what is going on :/

 

Did you run "New Permissions" listed under Upgrade Utilities on the Utils page of the GUI. My cache drive is set to nobody:users.

I edited the "sabToSickBeard.py" script file using Windows and copied over the folder to my proper cache drive folder also using Windows. I did not run into any permissions issues.

Yeah these new permissions seem to be doing much more harm than good for a lot of people. It seems the problem is that I copied the autoProcessTV folder as root - that's the only way I know how, using a telnet session! Is there any other way to access /usr/local as a named user rather than root?

 

I found some more notes  from my installation regarding permissions.

Maybe something here will help.

Just change to paths to suit your needs:

 

"find out who is the owner"

ls -al /mnt/usenet/apps/sabnzbd/

 

"change owner to nobody"

chown -R nobody:users /mnt/usenet/apps/sabnzbd/

 

"check the user rights" (the .py files should have read and execution rights for at least user and group)

ls -la /mnt/usenet/apps/sickbeard/autoProcessTV

 

Thanks for all the help - those commands allowed me to add the folder to sab, so hopefully it will just work now, even though I still can't actually edit anything using Windows! :)

I don't want to break your installation either. Check your SABnzbd config page. It needs to point to your autoProcessTV folder

 

Am trying to get it to do this, but I seem to be having some trouble with the cache drive. I can't write to it all of a sudden, even though I could fine before a reboot, and I also can't point SAB to it! Says it cannot access. The cache also has a 'Music' folder stuck on it that the mover refuses to move. How can a reboot break so many things? :S

 

The cache export setting is set to public, so no clue what is going on :/

 

Did you run "New Permissions" listed under Upgrade Utilities on the Utils page of the GUI. My cache drive is set to nobody:users.

 

Yeah, it looks like the problem isn't the entire cache drive, but anything I move to it as root (ie via telnet). The problem is that if moving a file from RAM for instance, via telnet as root is the only way I know how!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.