SABnzbd Forums

I don't think it's the same problem.
Despite the title, the problem was that downloading paused spontaneously (due to incorrect free space).

Are you sure you're not using the "Force" priority?
Also "force" is used to fetch additional par2 files.
Both will ignore the paused status.

Don't reuse subjects.
If your problem is really the same, it would be solvable in the same way.

i'm back lol
i just noticed it started happening again :-)
haven't changed a thing for weeks!
i will try and redo the whole try and error procedure lol

[Edit]
ok, i can confirm. once i disable the free space check (config-folders->Minimum Free Space for Temporary Download Folder: "0") than saving and hitting the pause-button it pauses as it should.
changed it back to 100M, saved, and it works again.

so it can't be the kernel i updated the last time. is there a way to "fix" this behavior from the OS site?

Despite the title, the problem was that downloading paused spontaneously (due to incorrect free space).

actually the problem was that the download "un-paused" spontaneously/by itself , due to incorrect free space report from OS? (i guess) :p

I had to disable the Usenet server in the server settings to get it to pause properly.

i think its the same problem, i too had no other way back then to stop/pause the download than to disable the server.

Celox wrote: actually the problem was that the download "un-paused" spontaneously/by itself , due to incorrect free space report from OS? (i guess) :p

OK, I must have misinterpreted the whole issue then.
Even stranger, because despite any errors in the disksize,
SABnzbd does not resume automatically when more space is available.
People have asked for this, but it doesn't do that.

So we're talking about you pausing the downloading manually
and SABnzbd deciding 4 seconds later to resume downloading?

So we're talking about you pausing the downloading manually
and SABnzbd deciding 4 seconds later to resume downloading?

exactly! 

shypike wrote:

Celox wrote: actually the problem was that the download "un-paused" spontaneously/by itself , due to incorrect free space report from OS? (i guess) :p

OK, I must have misinterpreted the whole issue then.
Even stranger, because despite any errors in the disksize,
SABnzbd does not resume automatically when more space is available.
People have asked for this, but it doesn't do that.

So we're talking about you pausing the downloading manually
and SABnzbd deciding 4 seconds later to resume downloading?

Yes! And the status is still paused when queried over the API or looking at the web interface.