Can't resume after freeing disk space

[ronnie3011]

Hi,

I'm running SABnzbd 2.3.9 on Win 10 64 bit. SABnzbd will pause my download queue when I run out of disk space, but after I free up space, I'm not able to get the downloads to resume, without restarting SABnzbd. Additionally, I've recently set the 'minimum free space for temporary download folder' option, in the hopes that it will pause before running out of space, and allowing me to manually resume once I create more, but I've noticed that it doesn't seem to respect that setting, nor allow me to unpause it afterwards.
The unpause button can be clicked, but my download speed stays at 0 kb/sec and none of my download progress bars proceed. The only resolution is a restart of SABnzbd.

[safihre]

Could you enable +Debug in the Status and Interface settings window and then after it happens again that you can't start it up again, send me the logs at safihre@sabnzbd.org?

[ronnie3011]

Thanks safihre. Is there anyway for me to clear or delete my existing logs, before I enable debug and start with fresh logs?

[safihre]

You could delete the existing log files in your sabnzbd Admin directory (where your sabnzbd.ini is). Listed on the first page of the Config!

[ronnie3011]

So I've been trying to replicate this issue for the logs, but after having this issue for a couple of years, it seems to be working correctly now. I think I isolated the specific issue though, which is different than how I originally framed it.

Generally, I have a lot in my download queue, and I keep the queue paused, and prioritize certain articles by marking them as 'forced' priority. What seems to happen is that SABnzbd pauses my queue once I have less than 4gb free space, as per my settings, but 'forced' items continue to download. Once the drive has 0 bytes of space left, the system does a hard pause, of sorts, where it no longer attempts to download forced items, as it has no where to download too. After freeing space on the drive, I'm unable to get it to continue, even if I unpause or mark the items back to normal priority, and then back to forced priority.

I'll work on replicating this specific issue and getting you logs.

[ronnie3011]

I've emailed you a log as well as step-by-step instructions of what I witnessed and actions I took to try to resolve it.