SABnzbd Forums

Version: 3.5.0 [a756eea]
Python Version: 3.10.1 (tags/v3.10.1:2cd268a, Dec 6 2021, 19:10:37) [MSC v.1929 64 bit (AMD64)] [cp1252]
OpenSSL: OpenSSL 1.1.1l 24 Aug 2021


If I have a problem with a download of a specific release that has already finished downloading and is showing in my history and queue up another nzb with the exact same name and then, after it starts downloading (override the dupe warning), delete the bad one from my history it messes up the new one which is currently downloading and I cannot recover it, I have to delete the new one as well and start all over.

The first error when deleting the item from History is:

Disk error on creating file E:\Path\Incomplete\ReleaseName\FileName.ext

This error Pauses the client (not the item, the entire queue). Restarting the queue triggers additional errors:

Disk error on creating file E:\Path\Incomplete\ReleaseName\DifferentFileName.ext
Saving \\?\E:\Incomplete\ReleaseName\__ADMIN__\SABnzbd_nzo_z5ug7n28 failed

The client then pauses again. If I try to resume again, it just barfs:

Error importing <NzbFile: filename=FileName1, bytes=xxxxx, nzf_id=SABnzbd_nzf_zc_ea4dd>
Error importing <NzbFile: filename=FileName2, bytes=xxxxx, nzf_id=SABnzbd_nzf_zc_ea4dd>
Error importing <NzbFile: filename=FileName3, bytes=xxxxx, nzf_id=SABnzbd_nzf_zc_ea4dd>
etc.
etc.

That can only happen if they were saved in the same directory in Incomplete, if so, how can SABnzbd know the difference between this new and old folder? They have the same name..
Maybe you can enable Debug logging and then after it happens again send me the log at [email protected].

They show up in different folders on my computer... if SAB isn't smart enough to be adding the ".1" and ".2" then it must be Windows... but then how does SAB know which folder to use?

I will capture some logs for you though :-)

Looks like there is a fix for this in 4.1.0. I'll test and see if it has solved this issue. :-)

Let me know if it doesn't!

Have not had a problem since. This seems to be totally fixed now. Currently running 4.2.0RC3 and have not had a problem since 4.1.0

Great