unpacking failed
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.
unpacking failed
It says this, but then i go to the download folder, and its there...unpacked. i dont get it
Re: unpacking failed
Does it give a reason?
SABnzbd does an extra check to find out if all expected files are actually unpacked.
Click on the job entry in History.
SABnzbd does an extra check to find out if all expected files are actually unpacked.
Click on the job entry in History.
Re: unpacking failed
Ok i looked deeper, and there is another problem. I put the mouse over the wrench and it said that craig ferguson unpacked, and then under it in the same wrench it says gumby failed, which is weird for gumby to be stated in that files wrench, and also, gumby never failed, it succeeded a day before, so why is it checking files from the past?
Re: unpacking failed
It isn't checking the past.
Very likely the NZB that you used contains some "extras".
Very likely the NZB that you used contains some "extras".
Re: unpacking failed
Can you be more specific to these extras? Because this is happening with almost every nzb completion. And its referencing only downloads i had previously. Its never referencing something i dont have.
Re: unpacking failed
I cannot make a consistent picture from what you describe.
So more info is needed.
Set logging to "Debug" level on the Status page,
download from an NZB that is known to cause problems.
Then get the log file from SABNzbd and email it to bugs at sabnzbd.org
Maybe a few screenshots would be useful.
Also add the URL of this post.
So more info is needed.
Set logging to "Debug" level on the Status page,
download from an NZB that is known to cause problems.
Then get the log file from SABNzbd and email it to bugs at sabnzbd.org
Maybe a few screenshots would be useful.
Also add the URL of this post.