Page 1 of 1
Sickrage postprocessing no longer being called
Posted: January 11th, 2016, 3:45 am
by hiker24
Since January 6 (probably after an upgrade of Sickrage), sabnzbd no longer seems to call Sickrage's postprocessing. The download in sabnzbd was successful and the history shows this:
the log says this:
Code: Select all
2016-01-11 05:09:49,023::INFO::[newsunpack:150] Running external script /usr/local/sabnzbd/var/scripts/sabToSickBeard.py(/volume2/2TB/Media/Downloads/Z-SabNzbd/complete/XXXXXXXXXXXXXXXX.HDTV.x264-LOL.nzb, XXXXXXXXXXXXXXXXXXX.HDTV.x264-LOL.nzb.nzb, XXXXXXXXXXXXXXXXXXXXXXXX.HDTV.x264-LOL.nzb, , tv, alt.binaries.teevee, 0, )
...
2016-01-11 05:09:51,095::INFO::[postproc:85] Saving postproc queue
2016-01-11 05:09:51,097::INFO::[__init__:919] Saving data for postproc1.sab in /usr/local/sabnzbd/var/admin/postproc1.sab
2016-01-11 05:09:51,098::INFO::[downloader:246] Post-processing finished, resuming download
2016-01-11 05:09:52,100::INFO::[nzbqueue:218] Saving queue
2016-01-11 05:09:52,102::INFO::[__init__:919] Saving data for queue9.sab in /usr/local/sabnzbd/var/admin/queue9.sab
2016-01-11 05:09:52,158::INFO::[__init__:919] Saving data for totals9.sab in /usr/local/sabnzbd/var/admin/totals9.sab
2016-01-11 05:09:52,161::INFO::[__init__:919] Saving data for rss_data.sab in /usr/local/sabnzbd/var/admin/rss_data.sab
2016-01-11 05:09:52,163::INFO::[__init__:919] Saving data for bookmarks.sab in /usr/local/sabnzbd/var/admin/bookmarks.sab
2016-01-11 05:09:52,165::INFO::[__init__:919] Saving data for Rating.sab in /usr/local/sabnzbd/var/admin/Rating.sab
2016-01-11 05:09:52,170::INFO::[__init__:919] Saving data for watched_data.sab in /usr/local/sabnzbd/var/admin/watched_data.sab
2016-01-11 05:09:52,175::INFO::[postproc:85] Saving postproc queue
2016-01-11 05:09:52,176::INFO::[__init__:919] Saving data for postproc1.sab in /usr/local/sabnzbd/var/admin/postproc1.sab
2016-01-11 05:09:52,178::INFO::[postproc:677] Queue has finished, launching: None (None)
No error reported or anything. Pasting the postprecessing call
Code: Select all
http://localhost:8081/home/postprocess/processEpisode?nzbName=XXXXXXXXXX.HDTV.x264-LOL.nzb.nzb&quiet=1&dir=%2Fvolume2%2F2TB%2FMedia%2FDownloads%2FZ-SabNzbd%2Fcomplete%2FXXXXXXXXXXXXXXXX.HDTV.x264-LOL.nzb
into the browser and calling it manually from there performs the proper postprocessing in Sickrage - so the problem might not be on the Sickrage side after all? (haven't changed anything with the sabnzbd config lately either).
SABnzbd Version: 0.7.20
Sickrage latest
running on a Synology NAS
Re: Sickrage postprocessing no longer being called
Posted: January 11th, 2016, 6:49 am
by shypike
I know very little of SickRage or SickBeard, but my first suspect would indeed be those.
BTW: your title says SickRage, but the script is SickBeard's. What's the relation?
Re: Sickrage postprocessing no longer being called
Posted: January 11th, 2016, 7:44 am
by hiker24
shypike wrote:I know very little of SickRage or SickBeard, but my first suspect would indeed be those.
BTW: your title says SickRage, but the script is SickBeard's. What's the relation?
AFAIK, SickRage is a fork off of SickBeard (so I guess that's why there are still SickBeard strings in the code)
Is there any way to debug sabnzbd and/or get more logging info to see why it fails to call the post processing URL?
Re: Sickrage postprocessing no longer being called
Posted: January 11th, 2016, 8:00 am
by safihre
What you see there is the output of the sabToSickBeard.py script, so it's not SAB that opens the actual link, it just calls the script.
Something goes wrong inside the script, for some reason it doesn't actually call that url.
There is nothing else in the (More) link?
Re: Sickrage postprocessing no longer being called
Posted: January 11th, 2016, 8:23 am
by hiker24
What do you mean by (More) link?
Clicking on the "View Script log" button in the sabnzbd history list says:
Code: Select all
Loading config from /usr/local/sabnzbd/var/scripts/autoProcessTV.cfg
Opening URL: ...
(with the URL from above) - so it seems to me the script is in fact called but stops on calling the URL (which does work however if used directly in the browser)
Re: Sickrage postprocessing no longer being called
Posted: January 11th, 2016, 9:07 am
by safihre
I took a quick look at the script and and the end it has:
Code: Select all
print "Opening URL:", url
try:
urlObj = myOpener.openit(url)
except IOError, e:
print "Unable to open URL: ", str(e)
sys.exit(1)
result = urlObj.readlines()
for line in result:
print line
So it's supposed to open the link and print the results.
For some reason when opening the URL, nothing happens for you.. I wouldn't know why.
You should go to the Sickrage forum's for this, there seem to be more problems with this so maybe you can find solution there!
Re: Sickrage postprocessing no longer being called
Posted: January 11th, 2016, 9:39 am
by hiker24
So basically you are saying that myOpener.openit(url) hangs and never continues (into the except block or beyond).
So well, something seems to be broken with Sickrage as well. Why I mentioned it on this forum was that the exact same URL works when called from the browser but not from sabnzbd - this is what I don't understand...
Re: Sickrage postprocessing no longer being called
Posted: January 11th, 2016, 10:22 am
by safihre
The difference is that you call the URL from your desktop while the script calls it from the NAS, so there is a difference.. But I'm no expert on what
