I think i can help with that - finally feels good to put something back into the community

 

set the install directory to  /usr/local/sickbeard  - this runs the apps in RAM

 

set the data directory to  /boot/config/sickbeard  - this is stored permanently on your flash drive

 

Do the same for sab and CP and you should be good to go.

 

At least thats how mine is set up and it works fine

 

I think i can help with that - finally feels good to put something back into the community

 

set the install directory to  /usr/local/sickbeard  - this runs the apps in RAM

 

set the data directory to  /boot/config/sickbeard  - this is stored permanently on your flash drive

 

Do the same for sab and CP and you should be good to go.

 

At least thats how mine is set up and it works fine

I hope the log files for those are not going to the flash drive also.  If they are I would move it off the flash drive.

Exactly. I wouldn't want those log files constanly hammering my flash drive. That's why mine goes to the cache drive. If you don't have a cache drive maybe you could put them on one of the other protected drives.

I am still running 4.7 and have no issues at all. I recently fell in love with SAB, SB, CouchPotato.  I was happy to see unraid plugins for these apps. 

 

Since I am running 4.7 I can just install these packages (SAB, SB, Couch) with unmenu.  However.... The package in this thread is for a beta version of unraid.  Running beta software really makes me nervous. 

 

Are there any advantages in upgrading to a beta version to run the packages in this thread or am I safer to just run  the unmenu packages for 4.7?

 

 

Thanks!!!!

well I've just rebooted the server and as usual the webGUI hangs when i start the array.

 

But this time instead of killing the sickbeard process i navigated to the /etc folder and did this

 

chown nobody:users sudoers

 

and SB came up no probs and the webGUI unfroze. i did this as i discovered that when i did a ls -l sudoers it was owned by root

 

this fixed it for me manually but can anyone here tell me how to fix it permanently so it doesn't happen again please?

 

thanks

 

You could add that chown to your Go script...

 

On a side note, for those having trouble starting Sickbeard and can't figure out why, I had the same issue. I figured out what the problem was. I set the SickBeard log file to "/var/log/" but the default permission on that folder makes it inaccessible to nobody. SickBeard won't start if it can't create the log file (Sabnzbd will btw). It will create the pid file which complicates things a bit (namely you have to delete the pid file to get it working).

 

To resolve, per another suggestion, I changed the log file to "/var/log/sickbeard" (and similar for sabnzbd).

 

Then I added a chown to my go script making these log folders accessible/editable to nobody.

 

The advantage of this is the log file is in RAM and you prevent a lot of writes to your cache drive.

just wondering how i can install sickbeard braches with this app.

 

off topic anyone know better way get special episodes from sickbeard or is it manual lookup

Upon restart (i.e. with these settings) the array does not start (it just shows 'starting' on the gui) and the packages do not function (no guy accessible). On one reboot the couch potato guy was accessible (with my data).

 

I was having the same problem with SickBeard not starting on boot and hanging unRAID in the Starting state.  When unable to find a fix here, I took a look at the plugin file and found a few issues that were causing this.

 

I made changes in the file to correct the problems and have attached the modified file.

 

Here is info on the changes I made:

 

The install directory was failing to get created

around line 181

FROM:

  mkdir -p "$(dirname $INSTALLDIR)"

TO:

  mkdir -p "$INSTALLDIR"

 

The SickBeard files were not not being copied to the install dir

around line 200

FROM:

  mv $(dirname $INSTALLDIR)/midgetspy-Sick-Beard-* $INSTALLDIR

TO:

  mv $(dirname $INSTALLDIR)/midgetspy-Sick-Beard-*/* $INSTALLDIR
  rm -R $(dirname $INSTALLDIR)/midgetspy-Sick-Beard-*

 

 

Because of the previous two problems the install failed and the script got stuck in a loop waiting for the pid file to get created around line 87.

To fix this I added a check to verify the install was successful before attempting to start the script and check for the pid.

around line 82

FROM:

  CMDLINE="sudo -u $RUNAS python $INSTALLDIR/SickBeard.py -d -p $PORT --datadir $DATADIR --pidfile /var/run/sickbeard/sickbeard.pid > /dev/null 2>&1"
  echo -n "Starting sickbeard:  $CMDLINE"
  $CMDLINE
  echo
  
  while [ ! -e /var/run/sickbeard/sickbeard.pid ]; do
sleep 1
  done
  
  echo -n "please refresh the page"

TO:

  if [ -e "$INSTALLDIR/SickBeard.py" ]; then
    CMDLINE="sudo -u $RUNAS python $INSTALLDIR/SickBeard.py -d -p $PORT --datadir $DATADIR --pidfile /var/run/sickbeard/sickbeard.pid > /dev/null 2>&1"
    echo -n "Starting sickbeard:  $CMDLINE"
    echo "Starting sickbeard:  $CMDLINE" | logger
    $CMDLINE
    echo
  
    s=0
    while [[ $s < 60 && ! -e /var/run/sickbeard/sickbeard.pid ]]; do
      sleep 1
      ((s++))
    done
  
    if [ -e /var/run/sickbeard/sickbeard.pid ]; then
      echo -n "Please refresh the page"
    else
      echo -n "SlickBeard Start FAILED"
    fi
  else
    echo "SickBeard Install FAILED"
    echo "SickBeard Install FAILED" | logger
  fi

 

You can either make the edits or use the attached file

 

Greg

sickbeard-0.4a-i468-1bw_plg.zip

Thanks - still no joy. Going to have to try another option which is a shame as I like the plugin approach. Unfortunately nothing seems to work in my case.

Thanks - still no joy. Going to have to try another option which is a shame as I like the plugin approach. Unfortunately nothing seems to work in my case.

 

There were still problems in the changes I made. I think I have it all fixed now and I'll post the updated file tomorrow.

 

 

 

 

Sent from my iPhone using Tapatalk

Attached is the updated file, this one is working better

 

Greg

sickbeard-0.4a-i468-1bw_plg.zip

Unraid and linux newbie here 

 

I am having an issue that is driving me nuts. I have a new build, a 2TB Parity, 2x 1.5TB Data drives and a 320GB cache drive. I only have unMenu installed, and Sabnzbd/Sickbeard/Couchpotato installed via plugin from the first post of this thread.

 

The settings:

Enable sabnzbd: Yes

Install directory: /usr/local/sabnzbd

Data directory: /mnt/cache/.sabnzbd

Port: 8082

Run as user: nobody

 

The issue:

I was able to use Sabnzbd to download a file. Once it was finished I was NOT able to see the file in the Cache Drive folder when navigating through Windows File Explorer via a laptop or Finder via macbook air. The only way I could see if the file was to navigate via the browser to "/mnt/cache/.sabnzbd/Downloads/complete". What am I missing that does not allow me to view the file from a laptop?

 

My setup:

- Unraid 5.0b12a (also I've tried Unraid 4.7 with Sabnzbd et all via unMenu. Again it worked but could not see the file.)

- I have both Movies & TV Shows setup to use the Cache Drive

- I have re-scheduled the 'Mover Settings' to run at a different time and I also initiated 'Move Now' without any success

- Tower connected via giga ethernet connection

 

Also when setting up Sabnzbd I used this guide http://lime-technology.com/wiki/index.php?title=Install_Python_based_servers. When getting to the "/mnt/cache/.custom/sickbeard/autoProcessTV" I don't see the "sabToSickbeard.py" file.

 

Any help is greatly appreciated...and sorry for the long post, I wanted to get as much information out.

 

The issue:

I was able to use Sabnzbd to download a file. Once it was finished I was NOT able to see the file in the Cache Drive folder when navigating through Windows File Explorer via a laptop or Finder via macbook air. The only way I could see if the file was to navigate via the browser to "/mnt/cache/.sabnzbd/Downloads/complete". What am I missing that does not allow me to view the file from a laptop?

 

 

I'm assuming you can't find the sabnzbd folder at all when navigating through File Explorer or Finder. The reason being is that because the file starts with a "." it is a hidden folder.  If you change the view type in File Explorer to show hidden files, you can see it.  In Finder, if you type in the entire string "/mnt/cache/.sabnzbd/Downloads/complete" it should take you to the folder.

I really need help. Everything was working great last night then this morning I had to restart my server to finish installing the last disk. now I cannot get isckbeard to run anymore. When I click apply it never starts the service. SAB started fine. I tried to do the chown on the /etc sudeors folder and now I am getting security error emails. I tried to use the installer posted above but it wouldnt even get as far as trying to install sickbeard. I am on 5.0 beta14. I am fairly new to unraid and really want to get this working.

 

Thanks

syslog-2012-02-23.zip

Have a quick check in your sickbeard folder and see if it's simply thrown the files into the midgetspy folder. For some reason the installer doesn't move files, as has been mentioned before on the previous page (sounds like it's been fixed though). For some reason it might still be doing this.

 

I always have this issue when my server goes down. I need to recopy the files across after the plugin does it's job.

 

I now officially hate plugins. My server shutdown last night due to a power outage and of course the plugin script has run (why on earth does it need to?) which has overwritten - everything - to a fresh state. There goes all my settings and sickbeard DB.

 

Plugin design for unraid really is so messed up.

That is why I have my settings folder for my plugins on my cache drive. unRaid runs in RAM, if you loose power everything in RAM goes away.

Walnuthead, thanks for that updated plg. It fixed my problems.

 

One error(and I only noticed it because unraid was oh so happy to tell me) is on line 90 of the rc.sickbeard file you forgot a space between the $1 and the closing bracket.

 

if [ $RUNAS != $1]; then
	chown -R $1:users "$INSTALLDIR"
fi

 

needs to be

if [ $RUNAS != $1 ]; then
	chown -R $1:users "$INSTALLDIR"
fi

 

After I changed that no complaints from unraid anymore!

 

If anyone else is manually changing this in their rc.sickbeard that Walnuthead provided, also remember to change the same thing in the plg he posted. I almost forgot myself, would have been faced with the same problem upon reboot,

Hi all!

 

After a few issues, a re-build I've finally got couch potato back. One things is that the film images are no longer showing for existing or new entries!

 

Any ideas?

 

Thanks,

 

Alex

Hi all!

 

After a few issues, a re-build I've finally got couch potato back. One things is that the film images are no longer showing for existing or new entries!

 

Any ideas?

 

Thanks,

 

Alex

You lost Couchpotato's image cache. You'll need to refresh each movie by hand, or delete and re-add them.

Thanks - I tried deleting them and re-adding but they added without images again - perhaps it needs a restart after deletion?

 

Alex

Hi. I've tried installing sabnzbd and SickBeard, as per the instructions, above, but I keep running into the same problem: many of the dependencies are no longer at their specified URLs. This seems to be true for several packages that come from Http://conie.slackware.com/~alien/slackbuilds.com/..., such as python-cheetah-2.4.2.1, and python-yenc-0.3.

 

Could someone please provide a workaround, for this?

 

I am running unraid version 5.0b14, with unmenu installed.

 

thanks.

Hi. I've tried installing sabnzbd and SickBeard, as per the instructions, above, but I keep running into the same problem: many of the dependencies are no longer at their specified URLs. This seems to be true for several packages that come from Http://conie.slackware.com/~alien/slackbuilds.com/..., such as python-cheetah-2.4.2.1, and python-yenc-0.3.

 

Could someone please provide a workaround, for this?

 

I am running unraid version 5.0b14, with unmenu installed.

 

thanks.

 

Yeah the website appears to be down right now.

 

Workaround is getting the dependencies somewhere else. I have both installed already so I'll attach them here for you and anyone else that tries to install before the links are changed and website is back up. Also included are the modified plg files for sabnzbd and sickbeard. All I did was take out the download commands so it doesn't error out trying to download the files.

 

Just place the contents of sab_sickbeard_plugins in the root of your flash drive and then either reboot your server or run

"installplg /boot/config/plugins/<NAME OF THE PLUGIN>.plg".

 

Let me know if there are any problems, I'm a noob here too but pretty sure I have everything included that you need.

 

Download the packages here: http://db.tt/ZpHEfhA7

Thank you.

No problem, let me know if it works alright. If it does I'll PM benni-chan to see if he wants to post the link on the first page for any newcomers until things get sorted on slackware.

 

EDIT: Seems the packages are back up for download on slackware so people shouldn't need the download I put up. I'll still keep it there for now in case.

" I now officially hate plugins. My server shutdown last night due to a power outage and of course the plugin script has run (why on earth does it need to?) which has overwritten - everything - to a fresh state. There goes all my settings and sickbeard DB."

 

I have had this issue twice now and am reluctant to reconfigure a 3rd time without a better understanding of what I am doing wrong. I have a cache drive configured, and (thought) I set up correctly.

 

Install Dir:  /usr/local/sickbeard

Data dir: /mnt/cache/apps/sickbeard

 

Everything was working perfectly, then when I went to shut down for one reason or another, Sickbeard would not shut down successfully and hung the interface completely. I ended up rebooting and poof - nice new sickbeard. The next time I had a power outage (UPS on order) and same thing.

 

Thoughts? Does the plugin posted on the last page address this issue?

 

Thanks in advance!

 

 

The reason this most likely happens on a power outage is because the config.ini for sickbeard is corrupted becuase of the unclean shutdown.  There is nothing that can be done about that.