Sabnzbd on Fedora 18 - crashes on queue complete

[ikarius]

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 sabnzbd tree have execute permission. Unfortunately, sabnzbd keep falling over with the following error, once it goes to empty queue. The only similar issues I could find in the forums surrounded python files without execute permissions. I'm pretty confident this isn't my problem

So, here's the crash error:

Code: Select all

Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/threading.py", line 551, in __bootstrap_inner
    self.run()
  File "/usr/share/SABnzbd/sabnzbd/postproc.py", line 167, in run
    handle_empty_queue()
  File "/usr/share/SABnzbd/sabnzbd/postproc.py", line 651, in handle_empty_queue
    sabnzbd.QUEUECOMPLETEACTION(sabnzbd.QUEUECOMPLETEARG)
  File "/usr/share/SABnzbd/sabnzbd/__init__.py", line 761, in run_script
    startupinfo=stup, creationflags=creationflags)
  File "/usr/lib64/python2.7/subprocess.py", line 679, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.7/subprocess.py", line 1249, in _execute_child
    raise child_exception
OSError: [Errno 13] Permission denied

Now, I'm wondering if this might be a permission on my NAS, but I'm not sure how to address or track that down, based on the error I've got in the log.

Here's the mount statement for my NAS share from /etc/fstab:

Code: Select all

//homeserver/TV         /media/TV               cifs    password=mypassword,username=myuser,iocharset=utf8,gid=1001,uid=990,file_mode=0777,dir_mode=0777   1 1

Can anyone help me troubleshoot this?

Cheers
Ikarius

[sander]

Now, I'm wondering if this might be a permission on my NAS, but I'm not sure how to address or track that down

Easy to track that down: point the SAB complete directory (and other SAB directories) to your local system (not your NAS), and try again.

[ikarius]

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 download to sickbeard, and sickbeard renames and places it on the NAS. I already went through troubleshooting that, and I know what a permission failure on the postprocessing looks like. This isn't the same. So... back to mystery OS permission error.

[sander]

Then why the "My media is kept on a Synology NAS" and the posting of your CIFS settings to access the NAS?

[ikarius]

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 through my sabnzbd config again, I realized there's no other point where the NAS directories are referenced.

[sander]

Can you rule out sickbeard: get a .NZB from binsearch, put it into SABnzbd, and let it download.

[ikarius]

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

[sander]

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

How can sickbeard crash when it's not involved? EDIT: Maybe I don't understand sickbeard, but if you put a .NZB into SABnzbd itself, why would SAB talk to sickbeard afterwards? Or does sickbeard crash spontanously?

[ikarius]

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.

[jcfp]

Code: Select all

  File "/usr/lib64/python2.7/subprocess.py", line 1249, in _execute_child
    raise child_exception
OSError: [Errno 13] Permission denied

This 'permission denied' error is encountered when sab tries to run your postprocessing script. Its permissions/ownership/etc apparently prevent it from being executed.