Support Forum

Oy vey. Apparently I cannot type at midnight. What I meant to say was sabnzbd crashes, as per usual after a standalone .nzb download- no sickbeard handoff.

I've done that, and it successfully downloads, processes, and then sickbeard crashes a bit later.

Because I'd forgotten that the only point where sabnzbd touched the NAS was when it called the sickbeard postprocessing script. I knew I had run into an issue with it early on, and fixed the issue I found by altering my mount line. I wasn't certain at the time that I'd found all the issues. Going th...

Umm. Right. Just went back and looked at that. Forgot... nothing which sabnzbd "knows" about is NAS storage. Everything's local filesystem, including all download directories- complete and incomplete. Only time things go onto the NAS is post-processing, when sabnzbd hands off the completed...

So, I've set up Sabnzbd+ on fedora 18. I'm running version 0.7.11. My media is kept on a Synology NAS. I have disabled selinux on the fedora system, I have ensured all sabnzbd files are owned by the sabnzbd user (chown -R sabnzbd.media /opt/sabnzbd). I've ensured that all python scripts in the sabnz...