Your logs don’t show anything useful, just the report being added to the queue.
As mentioned before: Trace logs will show the full response from SAB. Depending on the failure reason SAB will sometimes not mark it as failed and only show an errro message. Sonarr required that it’s actually marked as failed to be treated as failed.
I’m really at a lost here. I’m ENABLING trace logs from the Sonarr console and the logs I’ve given you are from “C:\ProgramData\NzbDrone\logs”
What am I missing here? I thought the past logs weren’t useful because the failed download entry in question was not in the last 30 items in the SAB history. But the most recent logs I’ve posted is in conjuction with two items in the last 30 items in the SAB history, I’m sure of that.
Just one important clarification here, do I need to enable trace logging and recreate the issue (enable it before the issue happens) or will enabling it AFTER the issue happens show us useful logs?
Again, I’m following every bit of instruction you are telling me.
EDIT: The failure reasons for both of those episodes, by the way, is “aborted, not completed” according to SAB. I have the “Abort jobs that cannot be completed” feature of SAB checked.
are you sure sabnzbd is actually marking those those as failed? somtimes there are failures but sabnzbd still marks it as completed and that means sonarr wont deal with it automagically
if you post a screenshot of the history in sabnzbd for the 2 episodes your talking about its quite easy to tell if its the above problem
some of this is fixed in sabnzbd 8.0 (hopefully)
Well, here’s a screenshot:
I hope that tells us something. And as I’ve mentioned in this thread, this already happened multiple times and it seems to be random.
yea its not that problem, you can see on the right hand side, the icons are in red, so it will actually be marked as failed
the problem is where sabnbz has a failed download/extraction etc, but the icon/status shows as completed, in this scenario sonarr wont deal with it
There are a few Trace log event sporadically in the logs, but nowhere near the level that would appear if the trace logging was enabled for a period of time. Did you enable trace logging then immediately post the logs?
Clear your log files and post a couple minutes of trace logs (so there aren’t 100’s of lines of non-trace logs and we can see what SAB is returning).
In this case enabling it after is fine, but we need a few minutes of logs.
Is Check before download enabled?
Those look like they should be handled properly, but the logs will tell us more.
Yes, I did post the logs immediately after turning on trace logging. My bad.
Got it, I’ll clear the logs first and do trace logging again.
No, “check before download” is not enabled as I remembered that you recommended me to disable that in the past.
This: https://www.dropbox.com/s/4xorohtmeiugvpn/nzbdrone.txt?dl=0 is 6-minutes worth of fresh trace logging. Anything useful?
Has Sonarr already marked it as failed and blacklisted it? I don’t see it processing it, so it appears to have already.
In that case we’ll need trace logs of the removal from SAB’s queue to see which response SAB gives on removal.
I just checked and yes both are already in Sonarr’s blacklist.
How do I gather trace logs of the removal of these episodes from SAB’s queue? Should I simply remove them from Sonarr’s blacklist and re-enable trace logging?
Either grab something you expect to fail and let Sonarr go through the blacklisting process or wait for it to happen and grab the logs then, grabbing something that is likely to fail is probably the best bet.
So you’re suggesting enabling trace logging BEFORE I replicate the problem, right?
That’s actually the thing because this issue is not recreated easily. It’s randomly happening. Won’t removing these same released from Sonarr’s blacklist produce significant trace logs?
Correct.
No, Sonarr tells SAB to remove it from its history and adds it to the blacklist at the same time, removing it from Sonarr’s blacklist won’t do anything.
Can you suggest of any easier way to replicate this? I can’t leave trace logging enabled all the time until the issue fails since it will saturate disk space, right?
The easiest way would be to grab things that you expect to fail.
It will use a maximum of 51MB of disk space.
I grabbed that same blacklisted Constantine series and Sonarr was able to delete if from SAB’s queue. This simply means that this problem is really random as I’ve explained in my previous posts. It mostly happens when there are multiple releases in SAB’s queue. If you check the earlier posts of this thread, someone from the SABNZBD forums was explaining that this could be a “sync” problem between the two programs. Have you thought anything about that possible issue route?
Sonarr makes the request to delete it every time there is a failure, if it randomly doesn’t delete I don’t see this being a Sonarr issue, which is why we need to know what response SAB retrurns.
The post on the SAB forum eludes to Sonarr asking SAB to delete it and SAB is in a state where it can’t remove it, since it is flipping between queue/history, if that’s the case SAB should be telling Sonarr that’s the case (response from SAB indicates that it can’t be found), which we should be able to deal with, if SAB tells Sonarr it was removed then Sonarr needs to trust that it was actually removed.
Until we know how SAB is responding we can’t begin to look for a solution.
Finally, after months of keeping trace logging enabled I was able to capture a failed download that was not deleted from the SAB history. I’ve uploaded all the logs I can get, please download them from here for your reference:
The name of the release in question is “Continuum.S04E03.Power.Hour.1080p.WEB-DL.DD5.1.H.264-NZBgeek” and has been in the “Aborted, cannot be completed” stage in SAB. I’ve tried searching for this text in all the log files and it seems that it is present in most of them which is why I decided to just upload all the files to you, just to be sure.
Thanks.
I’m expecting to see an event in the logs that shows Sonarr attempted to delete it, but I’m not seeing one. Is there a failed download event in Sonarr’s history?
The message I expect to see is similar to this:
[Continuum.S04E03.Power.Hour.1080p.WEB-DL.DD5.1.H.264-NZBgeek] Removing download from DOWNLOAD_CLIENT_NAME history.