SABnzbd Forums

After upgrading to 2.3.0 (Windows 10), completed download folders have been getting these bin/cue files (eg. 2_8EA1C807A8160B3A6545BA08E30C52E7.bin and 2_8EA1C807A8160B3A6545BA08E30C52E7.cue).

Inside the cue file the contents are like what's below. Shouldn't these be cleaned up automatically?

[Set]
Creator="Created by par2cmdline version 0.4."
Checksum=2227
[PAR]
U4&D5GNIKLETT=1922
SN&D5GRIKLETT=1957
QW&D5GVIKLETT=2002
OF&D5GZIKLETT=2067
2R&D5G5IKLETT=2172

Shouldn't these be cleaned up automatically?

Why?

BIN/CUE files are real content (meant to be burned to a disc). So they are not like rar/par files.

If you want you can tell SAB to delete them based on extension. See config -> switches -> cleanup_list

These files are normally cleaned up, strange that they were not. They are a byproduct of Multipar verification and repair.
In my tests they always get cleaned up, odd.
Could you enable Debug logging in the Status window, wait until you get a job that has files like this left over, and then click Show Logging. If you could send the log to me at safihre@sabnzbd.org?