Support Forum

Can't use SATA drives with my device, and putting incomplete folder on the micro-SD card with OS makes it unusable and sometimes crash. Haven't had any problems with USB external drives apart from deleting in this scenario, it's impractical in most cases but anyone using a small device has to do thi...

Changed the line, now debug log shows: 2019-03-28 13:48:18,098::INFO::[postproc:340] Starting Post-Processing on JobName => Repair:True, Unpack:True, Delete:True, Script:None, Cat:other 2019-03-28 13:48:18,105::INFO::[postproc:558] Cleaning up JobName (keep_basic=True) 2019-03-28 13:48:18,106::INFO:...

Interesting... just found out SABnzbd can remove the orphaned jobs entirely when deleting manually through the "orphaned jobs" section of the interface. So SABnzbd does have correct permissions to remove the files, it just doesn't. Any way I can find out why? Or should I wait until you mak...

Any idea if this is a bug, or I can do something about it?

Permissions for the __ADMIN_ folder itself are "drwxr-xr-x". All files inside are "-rw-------" with the exception of "-rw-r--r--" for "SABnzbd_attrib" and the .gz file. Files in job folder (in incomplete dir) are all "-rw-rw-rw-". For Incomplete fold...

Just checked and one more issue is preventing deletion - all files in the "__ADMIN__" folder are user read / write only, they're owned by the user / group SABnzbd is running as, but permissions aren't set.
Any way around that?

That did the trick - permissions are always correct now. Thanks so much, safihre!

It's already empty.

Every time SABnzbd is restarted, write permissions for the "Incomplete" folder are removed for the group it's running as and category "other" (anyone not the owner / group of directory). This happens even when SABnzbd is restarted via interface, regardless of its docker container...

SABnzbd is running inside a docker container for linux (from linuxserver), storage is on an external drive connected by USB (ext3 filesystem). Not running as root, but read/write permissions have been set and healthy jobs have no issues. If downloads have many missing articles, the job is orphaned i...

I see, all is well then. Ty for the reply. It seems jobs are orphaned instead of failed when the repair is unsuccessful, is that also normal? Small suggestion: setting the value over 100.2% is mainly good for cutting down repair time, but if there are more par2 files than 10%, it won't be equally as...

1/4.8 of the articles were missing for a download (according to missing articles in MB and total size in MB), which is about 20.8% and means only 89.2% are available. If I've understood correctly, below 100% out of 110% is impossible to repair. Why is the download continued? I have "fast_fail&q...