01:08:37,340::ERROR:: Cannot create backup file for /config/Ĭan you send me a screenshot of your unraid docker web ui for this container, left click the icon, select edit, toggle 'advanced view' top right and then screenshot and attach here. 01:08:04,296::ERROR:: Cannot create backup file for /config/ OSError: Operation not permitted: '/config/' I found multiple posts about linux ACLs but I ran getfacl on the directories and that file and see no special ACLs and everything is set to 777. Below is what the event log for sabnzbd is throwing.
According to the logs its having problems saving the file but I checked as I made edits this last time and not only did the timestamp on that file change but the size increased. Everytime my sabnzbd restarts it loses everything and comes up unconfigured. Fix seems pretty simple, write to the sabnzbd. I am having a similar issue to the person above me. Since the HOME ENV is set to /config, these are defaulted to /Downloads/incomplete, which are absolute paths within the docker image of /config/Downloads/incomplete and /config/Downloads/complete instead of /downloads and /incomplete-downloads as intended. Can you please take a look at the nzbtomedia log file and advise?
#Sabnzbd default base folder manual
I can run a Manual post processing from SC and it finishes without issues. The result is the show file is not moved to the tv show directory. Sab dl's the file fine and the script does run, rename the file, but post processing request to SC is not working. The error is SickBeard: Failed to post-process - Returned log from SickBeard was not as expected.! The only change on my end is binhex pushed a new version of SC last week. Ln -sf /usr/bin/python3 Looks like something has changed again, the nzbtomedia script is failing. Newshosting has the fastest downloads, longest retention and best search results.
I took me a longtime to figure out the difference between the SABnzbd Docker environment and the root unraid test the script after resetting the link to python3
#Sabnzbd default base folder update
Initially on update of the script, the script failed to run (I believe the issue is that if failed to run within unraid and NOT within the SABnzbd docker). The reason for Switchblades request for the symlink is that we thought "python" didn't exist. So there should be no issue if python already exists and point to python3. The nzbToMedia script was recently made python3 compatible, this is why we changed from calling python2 to python.