Yesterday I installed the SABnzbd plugin, and I've been pulling my hair out trying to resolve a seemingly nonsensical permissions error. SAB will find a .nzb file in the "Watch Folder", process it, complete the download, create the destination directory in the "Completed Download Folder", but then will be unable to move the files. It gives the error: "Unpacking failed, write error or disk is full?" In SAB's main Downloads page, it shows that there is 1291.22 GB free (which is correct). In the SAB log file, it gives a similar error:
ERROR:: write error ( /media/<uuid>/downloads/_SABnzbd Complete Downloads/<destination_directory>/<filename>)
This doesn't make sense to me because the directory for the "Completed Download Folder" is owned by the 'sabnzbd' user. SAB is definitely running as this user. Also, as root, I can create a file as the 'sabnzbd' user in the destination directory (sudo -u sabnzbd touch /<Completed_Downloads_Directory>/test). If the 'sabnzbd' user can create a file in the destination directory, and SAB is running as the 'sabnzbd' user, then why can't SAB move the files into the destination? This is just killing me.
Here is my system configuration:
- OMV 0.5.30
- openmediavault-sabnzbd 0.5.4 (SABnzbd 0.7.16)
- OMV ARM Privileges: Nothing is checked
- OMV ARM ACL: Nothing is checked
- All permissions were set manually
- Permissions of destination directory:
drwxrwx--- 13 sabnzbd users 12K Jan 15 16:39 _SABnzbd Complete Downloads
- SAB process status:
sabnzbd 18593 1 1 16:37 ? 00:00:10 /usr/bin/python SABnzbd.py --daemon --pid /var/run/sabnzbd --config-file /home/sabnzbd/.sabnzbd/sabnzbd.ini
I have tried checking the Read/Write box for the 'sabnzbd' user in the OMV ARM Privileges and the OMV ARM ACL, but the result is the same. I would really appreciate any help with this. I know this isn't really an OMV issue, but before I migrated to the SAB plugin, the manually-installed SAB worked just fine with ACL privileges.