Support Forum

shypike wrote:Please email the NZB to bugs@sabnzbd.org, adding the URL of this message.

Will do. It would be great to understand why it's happening.

Yep, so here are the chain of events:

1) uploaded nzb to sab, it downloaded and failed to unpack
2) take the same nzb into newsleecher and download all the pars
3) drop those pars into the folder of the incomplete sabnzbd attempt and use quickpar and poof it repaired np.

Is there a way to just tell sab to download all pars, some of us have unlimited bandwidth and we don't care about the extra consumption. I have two NZB's that sab fails to extract, both of which I can (using the same provider), grab the pars and repair myself.

Yep I see that, I mean't from the admin under status... email sent with info you need.

So it happened again, but the logs don't go back far enough during the evening it downloaded it. In fact the debug logs only contain an hour or so.. Any way to get more log data

I'll grab logs next time i see it happen

Seems better, but alot still fail because sabnzbd doesn't grab the pars. Almost every failure i had over the past few days were able to be repaired and unpacked. Sab doesn't seem to try and grab more pars and try a repair. Is there any way to force it to grab all pars.

Thanks, will give it a shot

Is there anything that can be done to deal with the nzbs where there are misnamed rars? If i run quickpar against them, it fixes it all up and you can unpack. sabnzbd however just stops and won't do anything with it.