3/18/2023 0 Comments Sabnzbd obfuscated01: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. I am having a similar issue to the person above me. Can you please take a look at the nzbtomedia log file and advise? 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.! Is there a guide on how to solve this issue This keeps filling my cache drive. I am trying to figure out how to handle this, and thought I had it working correctly. The only change on my end is binhex pushed a new version of SC last week. For what ever reason it seems any obfuscated release is left in my complete folder. Ln -sf /usr/bin/python3 Looks like something has changed again, the nzbtomedia script is failing. I'm currently working on another thing for SAB, so no time yet to investigate this. First guess: double obfuscated, and SAB only does one run / one layer of deobfuscation. I don't know why SAB didn't do that on these files. 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 SAB downloaded it, and indeed the result is obfuscated files, which are rar files. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |