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.
I'm on macOS Sierra. I made a rock-solid sleep script for commandline. It works perfect in every condition, but not with sabnzb. It isn't spwaned correctly, see here:
<USERNAME> should be mine (ds)
2017-01-15 16:00:06,418::INFO::[postproc:85] Saving postproc queue
2017-01-15 16:00:06,419::INFO::[__init__:970] Saving data for postproc2.sab in /Users/<USERNAME>/Library/Application Support/SABnzbd/admin/postproc2.sab
2017-01-15 16:00:06,419::INFO::[postproc:815] Queue has finished, launching: <function run_script at 0x54ca530> (sleep-now.sh)
2017-01-15 16:00:06,419::INFO::[__init__:827] Spawning external command ['/Users/<USERNAME>/nzb-scripts/sleep-now.sh']
When you clicked 'Show logging' we automatically remove all API-keys/usernames/passwords to make the logs anonymous for sharing online.
If you were to look in the actual log you'd see your usernames there.
But: your script not launching is a separate problem.
What the thing could be is that with SABnzbd we include a module that triggers the system to stay awake during download and post-processing, so it might be that even though you fire the sleep command, SAB is actually firing a 'stay-awake' command..
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
