Problem running SickRage post process script (Exit 127)

[stillhopeful]

I've been using SABnzbd in conjunction with SickBeard for a long time and everything has worked great so far. I recently switched to SickRage, mainly for its ability to handle failed downloads, and was able to replicate my setup successfully. However, as of this afternoon the post-processing script sabToSickBeard.py refuses to work and gives me the error message: "Exit(127) env: python2: No such file or directory". I am very confused as to why this is so as this script has worked for me before and I haven't changed anything in the .py file.

I have been toying around with NZBGet, which I installed yesterday just to try it out, and CouchPotato and am wondering if that might've impacted the script. In the move from SickBeard to SickRage I changed the Post-Processing Scripts Folder in SAB to point to /Applications/SickRage/autoProcessTV instead of /Applications/Sick-Beard/autoProcessTV but as I've said earlier this worked fine initially.

One thing I have noticed is that the first line in the sabToSickBeard.py, hellaToSickBeard.py and mediaToSickbeard.py scripts in the Applications/SickRage/autoProcessTV folder is "#!/usr/bin/env python2" whereas the first line in the autoProcessTV.py script is "#!/usr/bin/env python" (as opposed to python2). In the Applications/Sick-Beard/autoProcessTV folder the three scripts autoProcessTV.py, hellaToSickBeard.py and sabToSickBeard.py all have "#!/usr/bin/env python" as the first line and do not mention python2.

I am a n00b as far as python is concerned and so am asking this question again, even though I've seen similar questions on other forums online, as I found the solutions a little baffling. I've gone through all the options on SickRage and SABnzbd and can't figure out what the issue is. I would greatly appreciate some help with this issue as I'd like to continue using SickRage. Thanks.

[sander]

" as I found the solutions a little baffling." ... so what was the baffling solution?

[stillhopeful]

https://github.com/clinton-hall/nzbToMedia/issues/454 and http://stackoverflow.com/questions/1139 ... -directory talk about similar issues. I guess they don't offer a solution and so that was a poor choice of words on my part but the posts on both these threads are a little too technical for me. I don't understand the stuff about symlinks, for example.

[sander]

On my Ubuntu Linux 'python2' does exist. I didn't even know that. And 'python2' is a link to python2.7:

Code: Select all

$ ll `which python2`
lrwxrwxrwx 1 root root 9 mrt 17 14:00 /usr/bin/python2 -> python2.7

The plain 'python' links to python 2.7, which I did know:

Code: Select all

$ ll `which python`
lrwxrwxrwx 1 root root 9 mrt 17 14:00 /usr/bin/python -> python2.7

So, yes, linking 'python2' to python 2.7 or python2.7 is an easy solution. If you don't know how to create a link, tell us your operating system.

Or ... in the #!env line change 'python2' to 'python'.

[stillhopeful]

I changed the #!env line to python instead of python2 and the processing seems to work fine now. Don't know why it was broken for a bit, in that it worked fine when I initially setup SickRage a couple of days ago, and then had to be fixed. Thanks for your help.