SABnzbd Forums

let me start from the beginning though.  i selected my file to download this being a tv show (its always sunny in Philadelphia) and i put it in my que.  it then finished and moved the file to history, but on the left side where you should get the star it kept the little icon showing that it is working still for like an hour or more.  after a while it turned into a red skull and over to the right it said "nload failed - out of your server's retention?"

has anyone got this error before or knows what it means?


thanks for any help possible.

Sounds like the file was outside the retention for your server. News providers only keep uploaded files for so many days, after that they are deleted. The limit at which files get deleted depends on your provider, most keep files until around 100 days.

How old was the file you were trying to download?

the files that i tried to download were no more then 10 days old i believe.  i will have to check that when i get home.  but last night i was trying to download a show that was just on TV that night and got the same thing.  I tried to download it about a half hour after it was on.

Who is your Usenet provider? Did you restart sabnzbd between waiting for the file to unpack and getting that message?

Also can you please fill in the template provided here:
http://forums.sabnzbd.org/index.php?topic=44.0

Version = latest
Os = Vista 64-bit
Install = Windows Installer
Firewall = Vista
IPV6 = No
Is the issue reproducible? = yes

newsbin is the Usenet provider.  I am new to using newsgroups just to let you know. 

yes i have restarted sabnzbd and then got this message.  how long should it take to unpack an hour long tv show?

Not sure what you mean about newsbin being your provider.
newsbin.com = usenet software like sabnzbd
newzbin.com = nzb site

What I mean is like the provider you pay monthly, or if you get it through the ISP then your isp. Whatever you have put in as the host in the server page of sabnzbd's config.

Unpacking shouldn't take long at all, does this happen for every download? When it next happens you can send your sabnzbd.log file to [email protected] and we can tell you what is going on.

Also have a look in your download folder for a folder called "_UNPACK_Name of your download" and see if a file is being unpacked.

my bad, my provider is NewsHosting.

I was able to download about 15 files without a problem and then the next 15 and everyone now is doing this.

when i go into my completed download folder there is a folder called "_UNPACK_Name of your download" and the avi file is in there and the file will play on my computer. 

when i get home home i will send the log out.

If you have it on, try turning TV Sorting off and see if that helps.

not to resurrect an old thread...

but sometimes lately i too have been experiencing the exact same problem  as in the first post.

I am able to queue files without any issue and they seem to download fine.  Some may need to get a few more parts, but that is usually handled by par2 and autofetching.... but sometimes the unpack process takes ages to do and to clear the spinning action indicator on the left i have to restart sab.  it then produces a red skull and says failed to unpack.

It is not a server problem and it is not a disk / folder permissions problem as i have made sure they are not indexed and have full permission to write.  At first i thought it might have something to do with the post proc unable to get the tv show titles and then rename and delete the files that are not wanted....

either way just i would ask.  80-85% it works great but 15-20% it gives the red skull error.


thanks

Have you tried to unpack the stuff manually?
What does unrar tell you?

when it errors with the red skull everything has unpacked correctly and i am only left with the avi file.  but for some reason it leave it in an _UNPACK directory or _FAILED directory and will not rename the avi file according to the "TV sorting" presets.  i will also add that it moves the _UNPACK folder to the appropriate folder in the categories config.

You can check for warning reports in the log files (Config->Connections).
It is a bit of a puzzle.