Search Computer Help Please

Sunday, October 2, 2011

Installing Sickbeard on Synology NAS - Newbie Guide

** Please Note , SickBeard is now available through the SynoCommunity under the other sources tab**

Sickbeard has become very a popular PVR application to help you organize and mange your TV show.  It has the ability to grab your favorite shows as soon as they are available. For more info on sickbeard visit

This is a step by step guide on how to install Sickbeard for your Synology NAS ( this example was performed on a Synology DS211J 2-Bay NAS)

* Important to note that Sickbeard won't work on its own its more like an addon for Sabnzbd and helps to organize your TV shows and makes it hassle free. In this guide I am assuming that you have installed Sabnzbd successfully. If not I will hopefully get around to writing a walkthrough later on but if you do a bit of googling you will see that it can be done quite easily through package management.

Installing Sickbeard

the very first step is to login to your synology NAS, via the IP address example (my ip is visit in your browser where you will be asked to login to the Synology web interface

Login with the account you created when you setup the NAS, Goto Control panel and under Terminal Make sure that SSH is enabled.

Now you can login to your server using a SSH client such as (Putty) connect to the ip address of your server. When prompted for username/password , enter the username as root and password as the password you used when first setting up your synology. **Important -- if you don't login as root user you will have permission errors when trying to compile packages later on.

Step 1. Install IPKG Bootstrap

the first step is to install the boostrap on your system,  you will need to get the correct boostrap that corresponds to the kind of CPU your NAS has.

you can find out which CPU your nas has at

Find out which Bootstrap my NAS uses

Once you've found the one you need , download the boostrap file in .xsh format from

Download your Bootstrap

Once you've identified which bootstrap you need , copy the link to the boostrap download jump onto putty and login to the server. Navigate to a temporary folder so that you can unpack and install the boostrap. (remember these instructions are specific to the ds211j so remember to double check the boostrap you are installing)

mkdir -p /volume1/@tmp
cd /volume1/@tmp/




ipkg update
ipkg upgrade

You will need the git package to install updates for Sickbeard as they are released.

ipkg install git

Now navigate to the directory you wish to install SickBeard in 

mkdir /volume1/@tmp/Sickbeard
cd /volume1/@tmp/Sickbeard

Download and install the latest version of Sickbeard

git clone git:// sickbeard

Now you need to edit the start up script to set SickBeard to start automatically 

vi /var/packages/sab2/target/scripts/

This is where a lot of people get stuck using the linux vi editor , the above line will get you into the config file.  If you use the down arrow to get to the very bottom and start typing you can hit enter to reach the next line.

  Add the following line to the file 

$DIR/utils/bin/python /volume1/@tmp/Sickbeard/ --quiet & 

Once you have typed the above line into the file press the ESCAPE key, Hold Shift and Press :

to save and exit type wq and hit ENTER
to exit without saving type q! and hit Enter 

To Allow Sabnzbd to process your request from SB , type the following

ln -s /var/packages/sab2/target/utils/bin/python /usr/bin/python

Thats it for now, log back into the web interface and restart your device, Once your device restarts you should be able to access through http://devicenameorip:8081

Updating SickBeard 

To update SickBeard either manually or through the web interface you will need the following packages. The following packages will also correct the issue where SB can't find the GIT executable or get the error  Unable to find your git executable - either delete your .git folder and run from source OR set git_path in your config.ini to enable updates. also double check your config.ini file for the correct GIT path.

ipkg install coreutils
ipkg install git-manpages 
Then navigate to your SB installation directory and get the update

cd /volume1/@tmp/sickbeard/
git pull

Thats pretty much it for the SickBeard installation , the only thing left to do is to copy the contents of the folder autoprocessTV which is located in the sickbeard directory. goto the autoprocessTV direcotry and copy the contents into a the sabnzbd script folder

cp * destination_path  

remember to fill in the username/password if you have set one up for SB , inside the autoprocessTV.cfg file otherwise it will fail. To specify the script in sabnzbd 

goto Config -> Switches and select your desired script 
 there you have it , all done... any questions let me know

** Update **

New version of Sabnzbd 0.6.9

slight confusion, set your pre-queue user script to NONE

and under switches set the script for TV shows to , remembering to your sickbeard settings to make sure the tv category is set to use the script.


  1. Might want to change the entry:

    mkdir -p /volume1/@tmp
    cd /volume1/@tmp/




    ipkg update
    ipkg upgrade


    mkdir -p /volume1/@tmp
    cd /volume1/@tmp/


    sh syno-mvkw-bootstrap_1.2-7_arm.xsh

    rm syno-mvkw-bootstrap_1.2-7_arm.xsh

    ipkg update
    ipkg upgrade

    Else you get an error...

  2. thanks anon, will check it out the original worked for me at the time of this post , but i shall double check

  3. nice guide! The new ds1812+ is on its way.. gonna try this!

  4. Nice guide. Iam going nuts trying to figure out how to do this with my ds212+. Can you give me the steps or post what my changes would be? Thx

  5. your steps should be pretty much identical to the ones on this page, what part are you getting stuck at?

    have you enabled ssh? on the box

  6. I tried to follow your instructions, but SickBeard won't run. Or at least I cannot access it via port 8081.

    If I try to start it manually by logging into Diskstation using putty (as root), navigating to the directory where is installed; modifying the PATH to include (at the beginning) /opt/bin:/opt/sbin:

    then executing ./

    I get this on the screen:

    DiskStation> ./
    Traceback (most recent call last):
    File "./", line 44, in
    from sickbeard.webserveInit import initWebServer
    File "/volume1/Sickbeard/sickbeard/sickbeard/", line 26, in
    from sickbeard.webserve import WebInterface
    File "/volume1/Sickbeard/sickbeard/sickbeard/", line 30, in
    from Cheetah.Template import Template
    ImportError: No module named Cheetah.Template

    I have Python 2.7.2 installed. I had originally installed SABnzbd using the mertymade package; that installed a version of Python which I had upgraded subsequently.

  7. found a similar issue before apparently cheetah and python are installed but not linked

    Cheetah is installed in the python version you install it with.
    Open terminal and type cd and drag your Cheetah-2.4.4 (or whatever version you are on )into it:
    You get something like:

    Code: Select all
    cd /Users/User/Downloads/Cheetah-2.4.4

    After you are in the Cheetah-2.4.4 folder

    Then you need to install it, but instead of using: sudo python install
    You use:

    Code: Select all
    sudo /usr/bin/python install

    Type your (administrator) password and if all goes well, try starting SickBeard again.

    1. Thanks for your response. I tried adapting these instructions as I don't have (that I know of) "terminal". Rather I log into the Synology shell as root using putty and SSH. I found a single directory containing Cheetah:

      It contains two directories with Cheetah in the name:

      Changing to the Cheetah directory and executing the command above -->
      DiskStation> cd Cheetah
      DiskStation> sudo /usr/bin/python install
      -ash: sudo: not found

      Any other suggestions?

  8. hmm its hard to tell whats happening , can you post the contents of your File "./" , just so we can see what it thinks is its cheetah directory

    also line 26 and 30 , where you had the errors above

    1. The files seem long to post here. There were three different files mentioned in the error messages. I have Zipped them and put them on MS SkydriveLive. You should be able to access them at If that doesn't work, I can post the contents here but that is long.

      By the way, so far as the "sudo" command is concerned, since I am logged in as root, I executed without that. Turns out there is no file on my system.

  9. Are you away? Or having problems with the Zip'd files?

  10. OK, I have made some progress. Based on those error messages, and some other stuff, I decided that python didn't know about Cheetah, and the version of Cheetah I had was old, anyway. So, by following the instructions at with regard to installing Cheetah under Linux, I have managed to get Sickbeard running! Now comes the tweaking, and ensuring that it will start with SABnzbd, but at least I'm over this hurdle. Thanks for being available.

  11. Hey Ron , yep I was away for a bit

    i'm glad you had some luck getting sickbeard to start , good job. sounds like your all set

  12. My experience was the same as AnonymousMarch 24, 2012 7:54 PM post with regard to changing the 2nd and 3rd lines in the script.

  13. I've had to re-install the packages after putting larger HDD in my NAS, and discovered that the problem was different than above (and the fix simpler).
    First of all, I had to use the information from the post of March 24 with regard to the sh command (and rm) else I received an error message.

    Also, Another note: The links to python and the editing of have a dependency on the SABnzbd package that was installed. With the "mertymade" package, both of those need to be changed, since "mertymade" installs python in a different spot.

    In (note use of $UTILD vs $DIR)

    $UTILD/utils/bin/python /volume2/Sickbeard/sickbeard/ --quiet &

    and obviously the path to may be different in different installs also.

    and the symbolic link "path to original file" is also different with the mertymade package.


  14. Is this guide obsolete given that a Sickbeard package is available via the SynoCommunity and installable from the "Other Sources" tab in the package manager? I feel this guide ought to be updated with a warning right at the top to this effect. The version that's there is dated 3rd Jan 2013, I don't know when it was first made available via SynoCommunity.