hugbug wrote: ↑24 Apr 2018, 12:50
Check if you have download paths configured for categories.
Download item which was in the middle of the downloading may continue using the old destination. Does the problem occur for new downloads (which were in queued state after changing paths or added to queue after that)?
hey hugbug, same problem as OP.
Jobs that are in the queued state, which are paused (not even a single byte has downloaded), attempt to download and use directories that were configured at the time the NZB job was added the queue.
This becomes a problem in the event I find a download that will exceed the available space of my intermediate directory.
I change the intermediate directory in the config, save and restart, and if I just start the download again from the queue, it still downloads using the old intermediate directory.
as OP posted above, deleting the items in question, and re-adding them to the queue, it seems to follow the new config.
However, this can't be the correct behaviour, as it makes perfect sense for NZBGet to follow the config as configured, at the time the download job starts, not at the time of adding the NZB job.
Thoughts?