Jobs won't fail depending on availability

[yell0]

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" on, though I've tried it off, and req_completion_rate as the default 100.2% - still keeps going. Tried "Abort jobs that cannot be completed" as both on and off - keeps going.

Is this normal behaviour, and if so is there something I can do about it? Thanks for any help.

[safihre]

It depends on the size of the par2 files.
The 100.2 means that when the rar-files + par2-files are below 100.2% it will fail.
So if the job had 15% par2 the total size is 115% and it needs to have at least 15% of the data missing before it falls below 100.2%.

The fast_fail works based on 80% of the first articles. If all the first articles of each file happend to still be there, we will continue to download the rest of the files and use the 100.2% logic.

[yell0]

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 effective. Maybe anything over 100% scales up with size of par2 files, e.g. user sets 105% of 110% and it scales to 110% of 120%.

[safihre]

No, it's not normal for the jobs to be orphaned.
What system are you using SABnzbd on? Windows?
Where is the storage located? NAS or normally on the main disk?

[yell0]

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 instantly after download completion.

Can't post full log as it's recognized as a link, but here are some possible highlights:

Code: Select all

[nzbstuff:1179] Abort job "JobName", due to impossibility to complete it
[nzbqueue:782] [sabnzbd nzbqueue register_article] Ending job JobName
[sabnzbd assembler run] Removed job JobName
Starting Post-Processing on JobName => Repair:True, Unpack:True, Delete:True, Script:None, Cat:tv
Cleaning up JobName (keep_basic=True)
Purging data for job JobName (keep_basic=True, del_files=False)
[misc:1161] [sabnzbd nzbstuff purge_data] Deleting dir /incomplete-downloads/JobName/
[nzbstuff:1786] Folder not removed: /incomplete-downloads/JobName/
[database:272] Added job JobName to history
[database:261] Removing all but last 20 completed jobs from history
[bpsmeter:268] bps: 4528887.23672
[downloader:783] Thread 1@server: forcing disconnect
[postproc:94] Saving postproc queue
[__init__:959] [sabnzbd.postproc.save] Saving data for postproc2.sab in /config/admin/postproc2.sab
[downloader:301] Post-processing finished, resuming download
[nzbqueue:260] Saving queue

[safihre]

This is the problem: "Folder not removed"
I see we don't log the exact problem, I will fix that in a future release of SABnzbd.
For now you need to check permissions etc, since SABnzbd seems unable to do any removing.

[yell0]

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 restarting.

It only happens to whatever the "Temporary Download Folder" is set as - I've tried multiple different folders. Could this be a problem on the container's part? This only changes depending on what the "Temporary Download Folder" is set as within SABnzbd, docker volumes aren't inherently affected.

I've tried setting correct permissions after SABnzbd starts, and unhealthy jobs are then not orphaned, but they don't get repaired. They still get moved to the Complete folder. Anything created in Incomplete dir lacks group / other write permissions.

[safihre]

In Config > Folders, enable Advanced settings and then set the "Permissions for completed downloads" to empty.

[yell0]

It's already empty.

[safihre]

WHat if you use 777?

[yell0]

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

[safihre]

Great
Not a Linux guy at all, so was making and educated guess :p

[yell0]

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?

[safihre]

Hmmm not sure about that. Since SAB is the only one touching those.
Are the permissions of the parent folders correct?

[yell0]

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 folder itself "drwxrwxrwx".
Can't say for folders inside "__ADMIN__" as there aren't any.

Let me know if you'd prefer permissions written normally (if you don't know linux permissions).