In previous versions of SABnzbd any download that wasn't downloaded properly or didn't extract properly, etc. would be tagged as having failed and this made it easy to deal with failed downloads in post processing scripts. In the current versions certain failures will result in the download dir being tagged with _FAILED_ but some others will be left untagged. Is there nya way to change this behavior or use another method for dealing with _FAILED_ downloads in post processing?
Rob
[SOLVED] _FAILED_ tagged downloads
Forum rules
Help us help you:
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.
[SOLVED] _FAILED_ tagged downloads
Last edited by tret on April 5th, 2010, 10:51 pm, edited 1 time in total.
Re: _FAILED_ tagged downloads
So I discovered that SABnzbd passes the download status to python via sys.argv[7]. It looks as though it passes 0 for a successful job and 1 if there were any failures. Looks like this will work fine.
Rob
Rob