Downloads marked as 'Failed' but are repaired and complete.

[meemorize]

Hello.
I have noticed that starting in build 0.5.2 and also the latest 0.5.3 some of my downloads, most notably the ones needing repair are marked as failed downloads and post-processing is not being done on them. However SABnzbd does fetch new blocks, repairs the download and then marks it as failed after repairing it.

Going into the _FAILED_* folder I can simply extract the repaired release manually and everything works again but it seems there is a bug with downloads having been repaired but being marked as failed.

---

System:

• SAB Versions affected: 0.5.2 & 0.5.3
• OS: Mac OS X 10.6.3
• Install-type: OSx .app
• Firewall Software: None
• Are you using IPV6? No.
• Is the issue reproducible? It happens regularly, but I only have the one system and install to test on.

---

I am happy to try and bug test something if you have any suggestions.

[shypike]

Many NZBs contain multiple sets of files with their own par2 files.
Every sets needs to be OK, else the download is declared "failed".
Also there are sometimes issues with unpacking, these can trigger "failed" too.
Check the history and the log carefully for information.
If you happen to have a reproducably failing NZB, please send it to bugs at sabnzbd.org

[barabbas]

I've been having the same problem. I can't reproduce this with one specific NZB. It seems to happen with the earliest releases of tv shows on Astraweb. They've been having some troubles and a lot of downloads fail (or are said to have failed, that's the point of this post).
Sick Beard sends some show to sabnzbd, it gets downloaded properly, the folder gets renamed "FAILED", but the video and nfo files are in there. If I postprocess it with Sick Beard everything is fine, so the download is ok.
If I redownload the same NZB some hours later, it works fine, too.

So, different to the poster, in my case the files even get extracted, it's not that the archive files get copied. Everything is fine but the folder name (which wouldn't be so bad if Sick Beard didn't think the download had failed).

[shypike]

Is any reason for failure listed?

[barabbas]

I hope this is the relevant part and helps.

The message that is shown in the history is "ERROR: unable to find "Series.s05e10.720p.hdtv.x264-BLA.r13.100"" or sth like that.

Code: Select all

2010-11-29 04:36:57,880::INFO::[newsunpack:684] Par verify finished ok on e:\Usenet\downloadname\downloadname.vol00+01.par2!
2010-11-29 04:36:57,881::INFO::[postproc:271] Par2 check finished on downloadname
2010-11-29 04:36:57,904::INFO::[misc:837] Creating directories: I:\usenet entpackt\tv\downloadname
2010-11-29 04:36:57,907::INFO::[postproc:315] Running unpack_magic on downloadname
2010-11-29 04:36:58,677::INFO::[newsunpack:185] Unrar starting on e:\Usenet\downloadname
2010-11-29 04:36:58,680::INFO::[newsunpack:384] Extracting rarfile e:\Usenet\downloadname\downloadname.r13.1 (belonging to downloadname.r13) to I:\usenet entpackt\tv\_UNPACK_downloadname
2010-11-29 04:37:00,082::WARNING::[newsunpack:497] ERROR: unable to find "downloadname.r13.100"
2010-11-29 04:37:00,098::INFO::[newsunpack:384] Extracting rarfile e:\Usenet\downloadname\downloadname.r10.1 (belonging to downloadname.r10) to I:\usenet entpackt\tv\_UNPACK_downloadname
2010-11-29 04:37:00,200::WARNING::[newsunpack:497] ERROR: unable to find "downloadname.r10.100"
2010-11-29 04:37:00,201::INFO::[newsunpack:384] Extracting rarfile e:\Usenet\downloadname\downloadname.rar (belonging to downloadname) to I:\usenet entpackt\tv\_UNPACK_downloadname
...
2010-11-29 04:37:37,993::INFO::[newsunpack:416] Deleting e:\Usenet\downloadname\downloadname.r18
2010-11-29 04:37:37,993::INFO::[newsunpack:416] Deleting e:\Usenet\downloadname\downloadname.r18.1
...
2010-11-29 04:37:38,039::INFO::[newsunpack:384] Extracting rarfile e:\Usenet\downloadname\downloadname.r18.1 (belonging to downloadname.r18) to I:\usenet entpackt\tv\_UNPACK_downloadname
2010-11-29 04:37:38,039::INFO::[newsunpack:436] Archive e:\Usenet\downloadname\downloadname.r18.1 possibly encrypted, will skip content check

If not using SB, this is a cosmetic problem, as the download itself works, but in combination with SB it is somewhat annoying.

Will post more info as soon as possible, thanks for your time and your commitment.

[shypike]

SABnzbd passes on an error message from unrar "Cannot find volume".
The logging shows that for some reason it's using downloadname.r13.1.
".1" files are left-overs from a repair action or duplicate files in the NZB.
They should not be used at all.

Can you send one of these NZB files to bugs at sabnzbd.org ?
Please include the URL of this message.

[barabbas]

Would love to, but it only works when the server has incomplete versions of the files. When I try downloading the same NZB some hours later it works. So you would have to simulate a faulty connection or something like that. Anyway, I'll send you the NZB.

[shypike]

In that case it likely that these are repeired files.
The r13 files is the repaired one and the r13.1 the unrepaired faulty original.
So it seems that either SABnzbd sends these .1 names to unrar
or that unrar has some of its own reasons to expect them.
Anyway, I have now some info to start bug tracking.

BTW: do you see any .1 files ending up in your final folder?

[barabbas]

I did see some of these .1 files in my folder. I remember wondering how they got there, because I know that PAR2 renames files that way, but I never made the connection.

This problem started occuring about 1 or 2 weeks ago, I never saw it before that and I've been using SABnzbd for more than a year.

[shypike]

How is your setting of Config->Switches item "Enable Par Cleanup" ?
If this is off, then I can understand why the issue occurs.
(This option is an fossil that should be set to "on" always)

[barabbas]

Guilty as charged. Thanks, hope that will solve the problem.

I turned it off because of some weird download problem I had where I needed the PAR files but sabNZBd wouldn't keep them. If I don't report back consider this solved.

[shypike]

It's still a bug in SABnzbd though.
It shouldn't treat .1 files as valid RAR files.
The option will probably be removed in the next release.

[mr.sparkle]

Not sure if this is related but I got this error the other day:
"Unpacking failed, unable to find movie.part031.rar.2"

there are a few ".1" original files, none of which should be getting thrown into unrar, let alone a non-existant ".2"

manual unrar works fine

running 0.5.3 on karmic, pulling from astraweb, if that matters any

[shypike]

Besides repair these files can be the result of duplicate filenames in the NZB.
The same bug trips over these too.