newsbin.com

When restarting during a partly downloaded RAR-set, the whole set is moved to the failed files list and thus does not continue downloading. This problem was introduced with 6.31 and still exists with 6.40.

Select it in the failed list and hit Ctrl-Y. Likely it's the duplicate detector. If you don't use the duplicate detector, you can disable it.

Might have to defer entry into dup check till after the whole set gets downloaded.

It could also be related to your spam settings in the options. If none of these pan out, try renaming the downloads.db3 file in the data folder when newsbin isn't running. This will remove any files left in the queue, but it's possible something has gone wrong with the file.

DT

Yeah, when one RAR has been downloaded the whole set is moved to the failed files list after restart. Before 6.31 it would just continue downloading where it left off. It has also to do with duplicate, but it never worked like that before.

Hmm, don't see that, I think something else is going on. If you clear out your queue and get rid of the downloads.db3 file, does that fix it? Last session downloads just continue for me, and I use the duplicate filter.

It'll tell you why it failed it in the failed list. I'd look there.

I have been noticing this for some time, but assumed it was something I had done, as no one else had mentioned it. The items appearing in the failed list in my case are marked as Dupes, though I know I have never downloaded them before.

I will say as far as I can tell it doesn't always happen.

On looking at todays failed one common factor seems to exist

The rars are of the format

file.part01.rar
file.part02.rar
etc

and not

file.rar
file.r00
file.r01
etc

Though the latter format does appear in the fail list during normal operation. This may all be coincidence but may at least provide a clue.

As Quade mentioned, the reason for it failing is mentioned in the fail list. What does it say? I'm guessing duplicate match.

DT

I did say

"The items appearing in the failed list in my case are marked as Dupes"

I have been noticing this for some time, but assumed it was something I had done, as no one else had mentioned it. The items appearing in the failed list in my case are marked as Dupes, though I know I have never downloaded them before.

You did download them before, in the prior session. Remember one line in the download list might represent 50 files. So, on restart the dup checkers says, "file has already been downloaded before, reject it the second time around". If the file exists on disk, maybe I should ignore the dup check for that file and simply not download it again.

I was just looking and, at least in 6.4, if the file has a par and has already downloaded, it shouldn't signature match on restart so, this might already be addressed.

I will monitor in the next few days when I start a new batch of downloads, and report back If i see the issue again

IMHO, dupe check should be disabled for partial downloads after restart. The download would have failed before the restart if the file already was downloaded.

That's the intent, anything else happening would be an oversight.

DT