Newbie question: Where do the files go if no post processing?

[kathysmith]

Ok, I have a newbie question, and I read the help files, but still cannot find some files:
I am on XP, running latest release.
I passed an nzb file (for "widgets" lest say), the program did the downloading of the rar files just fine, but some were missing and I received errors on that. And then it failed on post processing because it could not find enough pars2 blocks to repair what was missing. OK, that is cool and as expected.

But, when I went to the temp folder where the files are supposed to be kept (and I see other partially downloaded files with their par files there in a folder named for the download name), I do not see a folder for "widgets" or any of it's par files that were downloaded. So where did they go?

The history says:
------------------------------------
Stage Download
    [Time-Taken]: 21 hours 33 minutes 47 seconds
    [Avg-Speed]: 77kB/s

Stage Par2
    [PAR-INFO] Widgets: => Not enough repair blocks left (have: 0, need: 676)
Stage Unrar
    [UNPACK]: => No post-processing because of failed verification 
-------------------------------------

But did sabnzbd erase all that was downloaded already? I was hoping to try and manually repair it with some hand done downloads and using Quickpar, but alas, no files.

There are a LOT of files in the cache directory, but they have nothing to identify them with Widgets.

Have I lost these files and just have to downlaod again by hand? 

Thanks in advance.
-kms

[kathysmith]

They should be in your completed download directory preceded with _FAILED_

Yea, that is what I thought as well from the docs. But they seemed to have simply disappeared.

Odd.

There was a _FAILED_ file for the previous download file (the folder had the name of the previously download file), but that named download did not actually fail, so I tossed that folder.

Any chance it named it wrong? Perhaps I tossed it but it contained something else?

Thanks. Sorry for posting in the wrong place, thanks for the move.
-kms

[kathysmith]

(Sorry for the long post, trying to give a lot of info here)

Ok, I just had another download fail, and this time it did leave a _FAILED_ folder. In fact, it left TWO _Failed_ folders, one labeled _FAILED_Widgets2B and one labeled _FAILED_Widgets2B.1. This was ALL from a single queue entry. The program complained not enough blocks again. There was also an empty  folder named Widgets2B in the CACHE folder as well.

The history said:

Stage Download
    [Time-Taken]: 11 hours 19 minutes 4 seconds
    [Avg-Speed]: 68kB/s
Stage Par2
    [PAR-INFO] Widgets2B: => Not enough repair blocks left (have: 0, need: 1551)
Stage Unrar
    [UNPACK]: => No post-processing because of failed verification

In the folder labeled ' _FAILED_Widgets2B.1' there was the nfo file, the par2 file, 17 PAR2 data files, and 43 various RAR files.  A QuickPAR on that folder did indeed show 1551 blocks still needed, just as sabnzbd said.

BUT...

In the other folder labeled ' _FAILED_Widgets2B' , there was an empty  Widgets2B folder (where it started to reconstruct I assume), and another 83 RAR files, the missing pieces from the first folder actually.

So, I dragged the contents of this second folder onto QuickPar, and it found sufficient blocks to complete. However, everyone of these RAR files from the second folder QuickPAR claimed was named wrong (although file name were correct.) QuickPar then said "Ready to rename 83 files" to complete the verification, and could do so without any problems. sabnzbd was unable to do this same thing.

Is this a possible bug in sabnzbd? Or maybe the equivalent of the QuickPar program it uses does not understand this failure? Why did it break the files up into two separate  folders?

At this point, I have had three failures in downloads this exact same way.

As an experiment, I took the same Widgets2B.nzb file I fed to sabnzbd and fed it to Newsleecher to download the same files, from the same server, again. The results was a complete download into a single folder, with no missing parts, no PAR2 files needed, and no renames required. (I thought it might be a problem with the nzb file at first.)

In the sabnzbd log, I see a number of lines like this (I only have Errors/Warnings turned on):

2008-08-24 04:07:28,530::ERROR::[nzbstuff] Error importing
2008-08-24 04:07:28,592::ERROR::[nzbstuff] Error importing
2008-08-24 04:07:28,592::ERROR::[nzbstuff] Error importing
2008-08-24 04:07:28,592::ERROR::[nzbstuff] Error importing
... etc...
2008-08-24 21:41:29,780::WARNING::[newsunpack] ERROR: unable to find "Widgets2B.part041.rar"
2008-08-24 23:44:00,655::ERROR::[postproc] Error removing workdir (E:\Cache\Widgets2B)

For each error line in the log, that same RAR part was put in the _FAILED_Widgets2B.1 folder instead of the main folder.

Is there something I am doing wrong here, or I have I uncovered some strange bug?

I will not delete anything for a few days in case there is something else you need to know or see, but this seemed to just start happening after a recent restart.

Now that I can reconstruct by hand, I can get past this, but thought you might like to know.

Thanks,
-kms

[switch]

Thanks for the detailed info. Could you send off a problem nzb file to bugs@sabnzbd.org please and I will look into it futher.

[kathysmith]

I assume the same info, right? Will do, thanks.
-kms

[kathysmith]

More clues?

I just had Widgets3B fail as well. This time, there was only one _FAILED_ folder, labeled _FAILED_Widgets3B. It was missing a lot of parts. In the CACHE directory was a folder labeled Widgets3B (no fail) and it contained most, but not all of the missing parts. Neither folder this time contained any PAR2 files, and 5 rar files were also missing. The history said:


Stage Download
    [Time-Taken]: 14 hours 18 minutes 45 seconds
    [Avg-Speed]: 83kB/s
Stage Par2
    [PAR-INFO]: => No par2 sets
Stage Unrar
    [RAR-INFO] Widgets3A: => ERROR: unable to find "Widgets 3A.part029.rar"

Strangely, part 29 was in the Cache folder, no errors.

Using the same nzb file, I was able to download those missing files from the same newsgroup and use QuickPAR to verify the results. There WERE Par2 files available in the nzb.

I wonder if I should uninstall and reinstall the program? Coould something have gotten screwed up in the parameters list?

Is it possible the error is on the import from Newzbin to sabnzbd? Maybe there is an error in the nzb file import? How could I verify this?

Hope this helps some.
-kms

[shypike]

We're looking at this, but repeating your downloads takes time.

Just checking: you are using Windows?
Can you also email your log files ?

[kathysmith]

Yes. XP. Log file on the way. Note I have the logs set to errors and warnings only.

-kms

[switch]

The specific download had no problems on my system, there was a few missing articles with giganews but it repaired fine.

As for your problems, I'm not sure. It's possible that sabnzbd got shutdown incorrectly during your restart and corrupted your cache files, however that doesn't explain everything. Sabnzbd only creates one folder per download job, and that folder is renamed along the unpack process, another one isn't created.

You log file doesn't contain any download info, but it has trouble reloading some of the files in the download, and quite a few connection issues. If you are still running into similar problems I suggest doing a full uninstall deleting all the settings and cache, and reinstall sabnzbd.

[kathysmith]

Thanks. I notice that after those few errors, it is working fine again. There were a few restarts and one crash in the middle of those fetches, so that could have been the problem. I appreciate your looking, and happy to hear it is not a strange bug.

Cheers,
-kms