Sonarr grabs the nzb’s correctly and sends them to sabnzbd, they are assign to the sonarr category however Sonarr itself will display the download in the Activity window for maybe 10 seconds and then it vanishes forever.
Manually changing the category in sab to something else and then back to sonarr does not cause it to appear on the activity nor get processed when downloaded.
5-5-31 15:17:19.8|Info|Sabnzbd|Adding report [Game.of.Thrones.S05E01.720p.HDTV.x264-DON] to the queue.
15-5-31 15:17:20.6|Info|DownloadService|Report sent to download client. Game.of.Thrones.S05E01.720p.HDTV.x264-DON
15-5-31 15:17:22.5|Info|Sabnzbd|Adding report [Game.of.Thrones.S05E02.720p.HDTV.x264-DON] to the queue.
15-5-31 15:17:23.3|Info|DownloadService|Report sent to download client. Game.of.Thrones.S05E02.720p.HDTV.x264-DON
Those are the two, the rest of the log file is RSS Sync, nothing more.
I’ve reinstalled both sabnzbd and sonarr along with generating new api keys repeatedly, no solution yet.
I renamed the logs folder so that it would start with fresh logs, changed logging to Trace. Did a restart of sonarr through System, Restart and everything seems to be working again.
So far I’ve told it to grab 3 shows, it’s grabbing and continuing to watch them, download processed properly and when a failure occurred it did exactly as expected.
Not sure what was going on. I know this entire machine was restarted last night.
For now I will leave Trace logging on as I have another show up tonight, i’ll let you know if it works or not. Thanks.
I’ve been seeing similar behavior with torrents. The logs were saying:
15-6-1 16:15:51.8|Trace|CommandQueueManager|Publishing CheckForFinishedDownload
15-6-1 16:15:51.8|Trace|CommandQueueManager|Checking if command is queued or started: CheckForFinishedDownload
15-6-1 16:15:51.8|Trace|CommandQueueManager|Command is already in progress: CheckForFinishedDownload
I reset the log files and set logging to trace and restarted of Sonarr through system (which happened to fail actually, I am going to open a separate thread for that one.) When it came back up it properly processed the download. That was the 3rd download that had an issue over as many days.