For certain download patterns, jobs that can't possibly complete (e.g., 90+% of content unavailable) will continue to download and end up with an "Invalid par2 files or invalid PAR2 parameters, cannot verify or repair" indication, rather than aborting early.
Version: 2.3.4 [2a113f7] on Windows Server 2016
Abort jobs that that cannot be completed - not triggering
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
-
- Newbie
- Posts: 16
- Joined: April 24th, 2017, 10:23 am
Re: Abort jobs that that cannot be completed - not triggering
Could you send me one of those NZB's at [email protected]?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
-
- Newbie
- Posts: 16
- Joined: April 24th, 2017, 10:23 am
-
- Newbie
- Posts: 16
- Joined: April 24th, 2017, 10:23 am
Re: Abort jobs that that cannot be completed - not triggering
By the way, I'm using Giga and Astra for NNTP service, if you're having trouble duplicating my experience...
Re: Abort jobs that that cannot be completed - not triggering
I replied to your email but see now that you used a throwaway address. So here a copy:
Are you sure you have the feature enabled? And what is filled for Config > Specials > req_completion_rate ?
When I try locally I see it try for a while, this job has a lot of par2 so it has to try a lot, and then give up after showing it's missing about 400MB.
What do you see?
I also have Astra and Giga.
Are you sure you have the feature enabled? And what is filled for Config > Specials > req_completion_rate ?
When I try locally I see it try for a while, this job has a lot of par2 so it has to try a lot, and then give up after showing it's missing about 400MB.
What do you see?
I also have Astra and Giga.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate