Some downloads fail due to misnamed rars

[dctrwho]

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.

[shypike]

Could be RAR5 format files.
Can you try 0.7.17RC1? See Announcements.

[dctrwho]

Thanks, will give it a shot

[dctrwho]

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.

[shypike]

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.

Please send an example NZB to [email protected]
(Please add the URL of this post.)

[shypike]

I cannot reproduce the problem, the thing downloads fine here.
What is possible is that par2 files are so much damaged that
both SABnzbd and the par2 program no longer recognize them as par2 files.
I would need a full debug log of this download from your system to
make any useful diagnosis for this.

[dctrwho]

I'll grab logs next time i see it happen

[dctrwho]

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

[shypike]

There are 5 log files.
"sabnzbd.log" is just the most recent one.

[dctrwho]

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

[swehawk]

There are a few threads on this topic, so I choose the latest one, even thought it's not been active for a good while now.

The problem with misnamed rar-files seems to increase. This last three nzb's I downloaded all had this problem which causes sab to fail but that Q-par fixes by renaming (no repair needed). This bugs me a lot, cause I not only have to run Q-par, but then have to manually unpack, rename and move (sab won't resume post processing after running q-par).

Is there a way to run a renaming-script directly after dowload completes and have sab resume post-processing after the script finishes?

The rar-files are named like: cfae28c9a3a433418afb12b504cae2ec.10 (starting at 10 gong to 100 plus) but par2 files have correct extension, so it wouldn't be too hard to make a script fixing this, but even better if this was built into sab itself!

Now, for sure I appreciate all the effort you people have put into sab, and it's one of my favourite apps, but this bug kind of spoils it

[sander]

@swehawk : out of curiosity, can you post or PM a link to such a NZB? I've never experienced what you describe.

[shypike]

The problem with misnamed rar-files seems to increase. This last three nzb's I downloaded all had this problem which causes sab to fail but that Q-par fixes by renaming (no repair needed). This bugs me a lot, cause I not only have to run Q-par, but then have to manually unpack, rename and move (sab won't resume post processing after running q-par).

SABnzbd should be able to handle this and we have taken measures to make sure it does.
Of course the reality of Usenet changes everyday and there might be bugs in SABnzbd.
So please do as Sander asked and email one or more sample NZB files to [email protected]
(Please add the URL of this message.)

[swehawk]

Ok, will do tonight!

[shypike]

I don't know which version of SABnzbd and which operating system you are using.
Your sample NZB works perfectly when I download it.