SABnzbd Forums

Hi.

I did use the switch "Download all par2 files" (Switches / Post processing) recently. I switched it off again but all the PAR2 files are still being downloaded. Well, at least partially, most of them have the strange (and incorrect) size of 700kB:



I couldn't find another bug report like this. I am using version 4.3.1 [41de133] on Windows 10 Pro 22H2 Build 19045.4412. I tried to reinstall SABNzbd already, but that didn't change anything.

Thanks for your help.

Can you share the name of your NZB?

Sure. It's "Stranded.Deep.MULTi6-ElAmigos{{404}}"...
But it happens with every item I download these days.

ScareYa wrote: ↑May 28th, 2024, 2:18 pm
But it happens with every item I download these days.

Also with the Test Download? Check via Wrench (upper right corner)

It sure looks like:



But at least not ALL PAR2s are of 700kB size...

Is there maybe a way to reset ALL SABNzbd configuration data? The "Restore defaults" button found in "Switches" doesn't help in this case. I tried.

Maybe deleting the AppData\Local\sabnzbd\sabnzbd.ini file or even the whole sabnzbd directory?

Yes:
Stop sabnzbd
delete the sabnzbd.ini
Start sabnzbd ... you should get the wizard. Fill it out

Can do that, but that might kill all chances to get more information about the bug in case you need it. I am perfectly fine to live with the bug for a while in case you should need some logs or whatever...

And btw: Thank you all very much for your time and effort investing in SABNzbd. You are the best!

ScareYa wrote: ↑May 28th, 2024, 2:39 pm Can do that, but that might kill all chances to get more information about the bug in case you need it. I am perfectly fine to live with the bug for a while in case you should need some logs or whatever...

Instead of deleting sabnzbd.ini, you can rename it to sabnzbd_notgood.ini.

Then follow the procudure. If it's working, do a diff on sabnzbd.ini and sabnzbd_notgood.ini

Good idea.
In a few minutes I will report back...

ScareYa wrote: ↑May 28th, 2024, 2:46 pm
In a few minutes I will report back...

You're a quick responder. Nice!

It's working now. My problem is solved. Thank you very much.

But in case you need more information from me I would be glad to provide it...
Maybe you're interested in the "faulty" sabnzbd.ini (without the access data of my usenet provider ofc)?

I might have found the culprit: In the "faulty" sabnzbd.ini the is a flag "enable_par_cleanup = 0" which is set to 1 in the working ini. I have no idea how that came to be...