Sonarr version (exact version): 2.0.0.5085 Mono version: 5.4.1.6 OS: Ubuntu 16.04 ((Debug logs)): https://pastebin.com/6V0ktZHj Description of issue:
Sonarr is leaving behind folders. Some of them have metadata, some of them have sample videos, and some of them are entirely empty. It doesn’t happen with all series, and it only happens some of the time. The included log shows the entries when I manually run the Housekeeping task, hope to clean up the directories in question, but I don’t see any pertinent information that would identify why certain directories are being skipped over or ignored.
I use NZBGet as a downloader, which downloads to a local Linux directory. Sonarr then moves the completed download over to an SMB share on a separate NAS, which is the image you see linked above.
These are folders Sonarr imported files from after your download client downloaded them?
That task cleans up data in the database, not random folders.
Sonarr should remove the folder after importing (if valid video files aren’t present, samples are ignored), debug logs from the import will show that Sonarr attempted to delete it.
The screen shot I shared is of the SMB share on my NAS, where Sonarr moves files to. It’s the final resting place for media that Plex uses.
NZBGet downloads files to an entirely different machine initially. So Sonarr is finding reason to move over those extra folders and then keep them, for some reason.
I couldn’t find any “attempt to delete” those extra folders in the log anywhere, but I also don’t know what I’m searching for. What are some reasons that folders would not be deleted? Keep in mind some are completely empty, some have a single .txt file, and others have sample videos.
Sonarr wouldn’t ever create a folder named that way outside of the series folder. You could search Sonarr’s logs for that folder name and see if it touched anything in that path, but given NZBGet puts downloads elsewhere and Sonarr wouldn’t create that folder, it’s not likely coming from Sonarr.
Usually because the folder has a valid video file in it (not a sample), but Sonarr could also try to delete the folder and not receive an error, so it assumes it was successful, but it silently failed, that has happened from time to time.
After reading your response, I tried to think it through cradle-to-grave, and I think the most likely culprit is NZBGet.
After post-processing, NZBGet deposits the “final product” into the same path that Sonarr is monitoring for TV Shows, so it’s likely something to do with post-processing in NZBGet.
This at least gives me something else to look into; thanks.
