Failed Download Handling problem

Yes, there is. This is the information for that event in Sonarr’s history:

Name:Continuum.S04E03.Power.Hour.1080p.WEB-DL.DD5.1.H.264-NZBgeek
Message:Aborted, cannot be completed

So it does have the same message as that of SAB’s but Sonarr did not attempt to delete it for some reason as observed in the logs.

When was that event created in Sonarr’s history, that will narrow down where to look in the logs since those actions both are triggered by the same event.

Sunday, September 20, 2015, 7:31 PM (GMT+8)

Unfortunately, the oldest event in the logs (nzbdrone.49.txt) is from: 15-9-20 20:28:02.7, an hour after history event, so we can’t see the attempt from Sonarr to SAB to remove the item and what the response from SAB was, which is what I’m assuming is the issue we’re trying to troubleshoot (60 posts later I’m not sure).

Is that because it was already replaced by newer events? I kept trace logging enabled the whole time until this event occurred.

Yes, by the time the logs were zipped up the oldest log was about 1 hour older than the history event, which we needed to see in the logs.

Another instance of the problem happened again and I really hope these logs will already show us the problem. This happened just now. Please check these for your reference:

The release that was not deleted by Sonarr is:

Blindspot.S01E06.1080p.WEB-DL.DD5.1.H.264-NTb-NZBgeek

I see two cases in the logs where Sonarr asked SABnzbd to remove a release with that name and in both cases SABnzbd responded indicating that the release was removed:

15-10-29 13:32:18.3|Debug|SabnzbdProxy|Url: http://localhost:8080/api?mode=history&name=delete&del_files=1&value=SABnzbd_nzo_ze979d&apikey=<removed>&output=json
15-10-29 13:32:18.4|Trace|SabnzbdProxy|Response: {"status":true}
15-10-29 20:21:13.7|Debug|SabnzbdProxy|Url: http://localhost:8080/api?mode=history&name=delete&del_files=1&value=SABnzbd_nzo_z-_rka&apikey=<removed>&output=json
15-10-29 20:21:13.8|Trace|SabnzbdProxy|Response: {"status":true}

So does that mean SAB is the culprit?

It looks that way.

How do I get guys from both sides to work together on this? Should I file another case on SAB’s forum?

I’m not sure there is much that is needed from us, your logs show the request from Sonarr to SAB and SAB’s response.