SABnzbd 0.7.16 is marking a download as failed although only the smallest .par2-file is broken.
All the other data- and par2-files are valid and working (verified with SFV and a recheck with the other PAR2-files with MultiPAR).
The debug-log has no errors or warnings.
At first MultiPAR is marking the first .par2 as good and all other par2s as "useless", but after verifying the data-parts, the first .par2 is found to be broken, while all the other par2-volumes are valid.
The NZB and a screenshot of MultiPAR have been sent via PN.
EDIT: After turning on the multi-core version of par2, the download is verified successfully. So this seems to be a bug in the classic par2-program.
sabnzbd falsely marking download as "Failed"
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.
Re: sabnzbd falsely marking download as "Failed"
There's something weird about this post.
Gone from the major servers and heavily damaged on the more obscure ones.
I'm currently on the road, but I will look into this one later.
Gone from the major servers and heavily damaged on the more obscure ones.
I'm currently on the road, but I will look into this one later.
Re: sabnzbd falsely marking download as "Failed"
FWIW, I got it without any missing articles with UseNetServer and Astraweb as backup.
Re: sabnzbd falsely marking download as "Failed"
Good to hear.
I have noticed in the past that sometimes damage to par2 files triggers erratic behavior in the par2 program.
Sometimes essential parts of a par2 file are damaged in such a way that the par2 program doesn't recognize them anymore.
I have noticed in the past that sometimes damage to par2 files triggers erratic behavior in the par2 program.
Sometimes essential parts of a par2 file are damaged in such a way that the par2 program doesn't recognize them anymore.