SABnzbd Forums

hey,

after a bunch of succesfull dls i always get this in my history:

Stage Download
    [Time-Taken]: ***
    [Failed]: Download failed - Out of your server's retention?
    [Avg-Speed]: **

when i take a look in my dl folder: no files there, but the program created traffic etc.

further in the warnings it says:

2008-11-09 05:32:48,015 ERROR [assembler] Disk error on creating file D:\Downloads\sabtemp\*.r46
2008-11-09 05:53:07,000 ERROR [assembler] Disk error on creating file D:\Downloads\sabtemp\*.r47
2008-11-09 06:13:37,265 ERROR [assembler] Disk error on creating file D:\Downloads\sabtemp\*.r48
2008-11-09 06:35:10,983 ERROR [assembler] Disk error on creating file D:\Downloads\sabtemp\*.r49
2008-11-09 06:55:26,671 ERROR [assembler] Disk error on creating file D:\Downloads\sabtemp\*.r50

and so on with all files it seems to have download but deleted? 

that out of retention error must be wrong because i can download all files whichs errored in sab with a different newsreader from the  same source.

whats wrong there?

Looks like SABnzbd is not allowed to write in the d:\downloads\sabtemp folder.

Is this literally what the log says?
I think you censored them a little too much.
Send your log file and a failing NZB to [email protected]

it just says the filename where i put the *.

Looks like SABnzbd is not allowed to write in the d:\downloads\sabtemp folder.

i see no reason why it shouldnt.
or do i have to give it specific folder rights in windows? guess not...

mail send.

You are sure your disk is not full? It's a 6G download.
The "out-of-retention" warning is confusing here, SABnzbd is not to allowed
to write any file to d:\downloads\sabtemp\banjo.
The result is an empty folder, so the post-processor thinks nothing has been downloaded.
That's all I can conclude so far.

We prefer not to troubleshoot older releases, please upgrade to 0.4.5 first.
Although there must be something wrong with your system.

ok i´v updated to 0.4.5 and set new paths to all folders.
i will give it another try now .. hopefully with files in my folder 

works now 

still a bit wired problem...

Had the same problem last night with the latest version.

Had plenty of space on the drive and 4Gb of download just disappeared.

Same message for all files as Flat.

[Time-Taken]: ***
    [Failed]: Download failed - Out of your server's retention?
[Avg-Speed]: **

Setup
Dual 2 GHz PowerPC G5, Leopard 10.5.5, SABnzbd+ v0.4.5, Safari 3.1.2 (had Plush interface running)

Have since downloaded some of the files and all was fine. I am new to SABnzd+ so not sure if it was something I did?!

chessman

Always check the log file for suspicious messages when something unexpected happens.

Could be any of a number of problems.
- Bad NZB file (sometimes they just don't contain required data)
- Server didn't have the articles (yet)
- Disk full
- SABnzbd doesn't have access rights to folders

Thanks.

I am suspicious that it was something I did. I was doing a lot of fiddling that night with schedules etc.

chessman

I had this problem as well today and I was puzzled. Till it hit me. The filenames and their paths together where to long! When I downloaded the files in a folder closer to the root it worked again.

Hope this helps!

Cheers

Edit: Oh and the same goes for the temporary folder. If [Path Temp] + [Filename] is too long it will fail...

Indeed, I forgot "pathname too long".
It isn't reported very well at this moment, we should do something about that.

shypike wrote: Indeed, I forgot "pathname too long".
It isn't reported very well at this moment, we should do something about that.

Has this issue been solved?

I am all of a sudden also experiencing the same. I´m running 0.5.0 Beta6.

We decided not to solve it for 0.5.0, we're too close to the final release.

It's a rather hairy subject, because every OS/filesystem has it own limits.
Most OS-es don't even report back the cause properly.

mvitos wrote: Edit: Oh and the same goes for the temporary folder. If [Path Temp] + [Filename] is too long it will fail...

Thanks for this information mvitos. I had the problem too but this information has helped me solve the problem. Will 0.5.0 fix the problem?

donmacp wrote: Will 0.5.0 fix the problem?

Please read:

We decided not to solve it for 0.5.0, we're too close to the final release.