Page 1 of 1
Abort jobs that that cannot be completed - not triggering
Posted: July 18th, 2018, 11:40 am
by NunyaBzness
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
Re: Abort jobs that that cannot be completed - not triggering
Posted: July 19th, 2018, 2:48 am
by safihre
Could you send me one of those NZB's at
[email protected]?
Re: Abort jobs that that cannot be completed - not triggering
Posted: July 20th, 2018, 7:31 am
by NunyaBzness
On the way
Re: Abort jobs that that cannot be completed - not triggering
Posted: July 26th, 2018, 2:03 am
by NunyaBzness
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
Posted: July 27th, 2018, 3:34 am
by safihre
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.