SABnzbd Forums

I never encountered this problem, but sabnzbd is constantly pausing over and over. It will pause, then I click resume, then it pauses within seconds after. How can I stop this?

I never dabble with the switches or anything but the complete/incomplete folder. Everything else is default.

Thank you in advance for any help. -adabo

Don't you get any warning about disk full?
Constant write errors would show the same behaviour.
Check the status page for errors and warnings.
Open the log file (also on Status page) and check the end for error messages.

Thanks shypike. I think the problem was retention on my server, even though I remember downloading older. Anyway, I chose a more current post and the download went as normal.

So you had a very low speed.
I assumed that the program went into actual pause.

No, it did pause. 100% stop.

0 speed is not the same as pause.
Pause is when the pause symbol at the top right is red instead of yellow.

Yes. The pause/resume button turns to "Resume" and the download speed color goes from green to red. It is definitely, positively, 100% no ambiguity, Pause.

Also, the status where it turns from green to red says "Pause".

So this would have nothing to do with out-of-retention downloads.
Does it work now with other NZB files?
No errors or warnings?
Because about the only thing I can imagine (apart from real bugs) is that
a specific NZB may result in bad writes (due to weird or very long files names).
You don't have a resume scheduled in Config->Scheduler?
Can you try the "bad" NZB again.
If it fails again, can you email it to bugs@sabnzdb.org? (please, add the url of this post).
Which operating system?

Sure. I'll email it. It is indeed still causing the pausing. And it seems that the retention theory does not hold up because I have downloaded much older. Thanks for your continued support in this matter. Hope I can help.

I wonder if it could be the long file name...

There is a "special" setting in the sabnzbd.ini file.
Described here: http://wiki.sabnzbd.org/configure-special
It's "folder_max_length", setting it to 64 solves most path size issues.
From that I deduce that you are using Windows.

The problem, it seems, was a disk write error due to the file name being 128 characters long ... O___O so I shortened it and it works now. Thanks again for the support and patience to sort this matter out.

Ahh yes, I forgot to respond to your question. Yes I am using windows 7 64.

Glad it's fixed now.
We are looking at a better solution for long paths, but it might take a while.