the issue is in the start of the nzbToSickBeard Script
#!/usr/bin/env python

Originally (v9.0) we passed python command (full path before the nzbToSickbeard command.

I removed this as it shouldn't be necessary, but I think i might put it back in after all...

from nzbtomedia.

Should work again now.

from nzbtomedia.

Still having issues actually :(

http://pastebin.com/PcER3eaJ

from nzbtomedia.

Ok... And you added the python path back into your settings?

Did this work with the old version?

from nzbtomedia.

Yes put python path back, with previous versions it worked perfect but upgraded to latest svn few days back after switching back from sab to nzbget

from nzbtomedia.

weird...

Can you try running the following via ssh? (from within the directory where these files reside)
./nzbToCouchPotato.py
python nzbToCouchPotato.py

What output do you get from each of those?

from nzbtomedia.

DS211> /usr/local/python/bin/python nzbToCouchPotato.py
nzbToCouchPotato V4.1
Invalid number of arguments received from client.
Running autoProcessMovie as a manual run...
Loading config from autoProcessMedia.cfg
waiting for 0 seconds to allow CPS to process newly extracted files
Opening URL: http://localhost:5082/api/apikeyhere/manage.update
CouchPotatoServer returned {u'success': True}
manage.update started on CouchPotatoServer for Manual Run
DS211> /usr/local/python/bin/python nzbToSickBeard.py
nzbToSickBeard V4.1
Invalid number of arguments received from client.
Running autoProcessTV as a manual run...
Loading config from autoProcessMedia.cfg
ERROR: In order to run this script manually you must specify a watch_dir in autoProcessTV.cfg
DS211>

from nzbtomedia.

And if you run with ./nzbToCouchPotato.py ?

According to the above these scripts should be called without problem.

from nzbtomedia.

. /nzbToCouchPotato.py only doesn't work. Makes me thinking that the last time it worked my Synology was bootstrapt and now it isn't. On the other hand were using python path var again so it should be working.

from nzbtomedia.

I presume you restarted nzbget after updating these changes (to put python path back in)?

from nzbtomedia.

Yes, i'll do a few more tests later today with and without bootstrap.

from nzbtomedia.

Is the python path var being used correctly after importing it back into settings ?
With path setting back the same error returns.

Edit:
Ok this is strange, after hitting the save button several times it seems it didn't saved the config correctly now it's saved correctly it does a bit more but still not functioning as expected.

http://pastebin.com/Guqp53is

from nzbtomedia.

Still same error...

How have you downloaded /edited these files?
Tis almost looks the the dos crlf issue.... If you run dos2linux on all these files, and ensure they are executable....
Does that make any difference?

I'll look at they way I re-added the python path... But that should be pretty straight forward.

from nzbtomedia.

There already linux format. Don't get it, worked perfect in version 9 before.

from nzbtomedia.

Ok... The dev branch (v10 support) really only changed the script that calls the nzbTo* scripts...

So, can you try using the v10 nzbget script, but the nzbTo scripts from the master branch?

Can you try using the nzbget v9.0 script (from either branch) with the nzbTo* scripts from dev branch, and then from master branch?

Note. I don't know what will happen using nzbget v9 script in nzbgetv10. It may not do anything if the tags are different...

from nzbtomedia.

The other change I made recently was to make these files executable.

Can you remove x permissions and then test?

from nzbtomedia.

Tested some , all failed.
But noriced a few bug fixes in latest version so going to compile revision 566 from nzbget and run it without any additional scripts first, if that works well i'm going to compare changes with latest dev branch scripts and report back.

from nzbtomedia.

AHHHH...

for v10 I actually reverted back to the default headers etc in nzbget-postprocess.sh

v9.0 had the following header
#!/bin/sh

-- coding: cp1252 --

So... try adding the line

-- coding: cp1252 --

into the new file.

from nzbtomedia.

I'll try but not sure if it will help since it isn't there in original file from nzbget ;)

from nzbtomedia.

Not tested yet but i noticed in log a few unrar errors.
When comparing original files here (rev 566, now 567) https://nzbget.svn.sourceforge.net/svnroot/nzbget/trunk/nzbget-postprocess.sh

I noticed this part
if [ "$NZBOP_UNPACK" = "" ]; then
echo "[ERROR] This script requires nzbget version at least 10.0-testing-r555 or 10.0-stable."
exit $POSTPROCESS_ERROR
fi

Specially this : This script requires nzbget version at least 10.0-testing-r555 or 10.0-stable

So i merged your code with original and came up with this, going to test in a few
http://pastebin.com/C9XSN1JK

from nzbtomedia.

That shouldn't make any difference to the way the script is called... In fact, that just provides an exit condition for using this script with an older version of nzbget.

The change that is stooping your script from running must be an environment change. I can't reproduce :(

from nzbtomedia.

What user is running nzbget?

I think importing the !# /usr/bin/env python
Is causing issues....

Can you do a test by removing this header from the 2 nzbTo* scripts?

from nzbtomedia.

The user NZBget running is nzbget:root
Scripts are nzbget:users

Will test in a few.

from nzbtomedia.

It looks like it can't find the correct processing scripts, in every log file i don't see any of this in it

"Script triggered from NZBGet, starting autoProcessTV..."

I see this in log
Post-Process: Post-processing script successfully started

But not that it triggers NZBget script.

I think i revert back to version 9 because NZBget almost always failes on par/unrar also.
Edit: Version 9 works out of the box.
Strange why version 10 is giving me such issues.

from nzbtomedia.

closing for now as it has been reported as working in v10 for others... if you get any more info, please re-open.

from nzbtomedia.