I don't understand what is going on. For the past few months, sabnzb has been reporting my downloads as failed, despite the fact that the downloads appear complete and intact in my selected download folder. It is to the point where I just ignore the fail notice and not even bother to check if something is wrong.
I look back at my download history. In just a few pages of history, I have four "failed" downloads. There is no reason given. No explanation listed in the UI. In every case, the download did complete and unrar successfully.
Any ideas what is going on? Is there some way I can get more info about these error messages? As I said, the UI gives absolutely zero information. All it does is show the red skull icon (I am using the default "plush" skin), and rename the destination folder to _FAILED_ETCETC.
Random "failed downloads" that didn't actually fail
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Random "failed downloads" that didn't actually fail
Usually the log file gives extra info.
If you look at this file right after a job "fails" and no other one starts,
the end of the log file should give you more info.
If you look at this file right after a job "fails" and no other one starts,
the end of the log file should give you more info.
Re: Random "failed downloads" that didn't actually fail
I looked at the log file for two downloads, both of which were marked as "failed". These downloads were sets of rar files.
In both cases, the exact same thing appears to have happened. For some reason, sabnzb created an additional rar file, then "failed" trying to unrar this file. In both cases, the rar file had the exact name as the final rar file in the download, except with a ".1" appended.
I will google around, but I currently have no idea why sabnzb is creating these files.
In both cases, the exact same thing appears to have happened. For some reason, sabnzb created an additional rar file, then "failed" trying to unrar this file. In both cases, the rar file had the exact name as the final rar file in the download, except with a ".1" appended.
I will google around, but I currently have no idea why sabnzb is creating these files.
Re: Random "failed downloads" that didn't actually fail
I just started a new download and took a peek at the file list as it was downloading. For some reason it is actually listing the final rar file twice! It appears that something is causing sabnzb to download the final rar file twice. Maybe it is a bug with the easynews nzb generator. I create my nzbs by using their web based interface.
I looked at the nzb itself in a text editor, and I see that one particular file is indeed listed twice. Very annoying.
I looked at the nzb itself in a text editor, and I see that one particular file is indeed listed twice. Very annoying.
Re: Random "failed downloads" that didn't actually fail
Duplicate files are almost impossible to handle properly.
We can overwrite existing files, that works if the correct file is the second one.
We rename the second one (current way of working), but that fails when the second file is the correct one.
We will be looking at using the repair capabilities of par2 more efficiently.
Possible that can help to lessen this issue too.
We could file a warning about duplicate files, that would at least make you aware of potential problems.
Anyway, the next major release will at least allow you to manipulate the files of
a failed download and then give you a change to retry post-processing.
We can overwrite existing files, that works if the correct file is the second one.
We rename the second one (current way of working), but that fails when the second file is the correct one.
We will be looking at using the repair capabilities of par2 more efficiently.
Possible that can help to lessen this issue too.
We could file a warning about duplicate files, that would at least make you aware of potential problems.
Anyway, the next major release will at least allow you to manipulate the files of
a failed download and then give you a change to retry post-processing.