Issues with Sickbeard Postprocessing

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
drewdatrip
Release Testers
Release Testers
Posts: 25
Joined: May 15th, 2010, 6:20 pm

Issues with Sickbeard Postprocessing

Post by drewdatrip »

Here is a little information as to the setup of my situation
I run Sab and sickbeard on my Synology DS210j i just recently upgraded the firmware to DSM 3.0 and had to redo my installs of SAB SB etc
Originally i removed the .sample from the cfg file and copy the files over to my nas into the script section of sab folder after i did a:

Code: Select all

chown =x on the subfolder and all its contents to make the scripts executable.
When i first did this post processing worked right out of the gates, however in this reinstall i am not having such luck im getting this error in sab:

Code: Select all

Cannot run script /volume 1/download/SABnzbd/scripts/sabToSickBeard.py
There is no further information in the sickbeard.log

i wrote a guide for myself with everything i did at first so im pretty much doing exactly what i did first time around
Anyone else run into a similar situation?
thanks

Drew
drewdatrip
Release Testers
Release Testers
Posts: 25
Joined: May 15th, 2010, 6:20 pm

Re: Issues with Sickbeard Postprocessing

Post by drewdatrip »

pair of dimes wrote: the first line of sabToSickBeard.py is #!/usr/bin/python right?

please type this in ssh shell and report the output:

Code: Select all

ls /usr/bin/python
if it does not list anything (as in there is nothing there) try running this:

Code: Select all

ln -s /var/packages/sab2/target/utils/bin/python2.5 /usr/bin/python
ls: cannot access /usr/bin/python: No such file or directory

Looks like you found the root of the problem. ill report back after a new show finishes

Thanks again pairdime

Drew
drewdatrip
Release Testers
Release Testers
Posts: 25
Joined: May 15th, 2010, 6:20 pm

Re: Issues with Sickbeard Postprocessing

Post by drewdatrip »

That did the trick!
So from what I understand the sabtosickbeard script calls on python that is located in a particular place on the system, however there was no python in that location.
The command linked the python ground in the sab package into where the script wants it

Is that right ?

Thanks

Drew
Post Reply