I don’t think my Failed Download Handling is working right. I’ve been monitoring it for weeks now and when a download fails, I get an entry in my log like I did yesterday like this:
[True.Blood.S07E08.Almost.Home.1080p.WEB-DL.DD5.1.AAC2.0.H.264-YFN] Download Failed, waiting for retry interval to expire.
But after the default 60 minutes, it never retries and/or marks the download as failed in the history section. My settings are all default for timings and such.
Which version of drone?
Which download client are you using?
That message is logged at the INFO level, but most are logged at the DEBUG level, please enable debug logging and post the latest file to pastebin after a few minutes of running at debug. https://github.com/NzbDrone/NzbDrone/wiki/Log-Files
I turned on Debug, waited a few minutes, and posted it to pastebin as requested. The file was far too large for pastebin so I had to arbitrarily copy the last third of the log – let me know if you need the whole thing.
14-8-12 10:25:25.8|Debug|FailedDownloadService|[True.Blood.S07E08.Almost.Home.1080p.WEB-DL.DD5.1.AAC2.0.H.264-YFN] Download wasn’t grabbed by drone or not in a category, ignoring download.
14-8-12 10:25:25.8|Debug|FailedDownloadService|[True.Blood.S07E08.Almost.Home.1080p.WEB-DL.DD5.1.AAC2.0.H.264-YFN] Download wasn't grabbed by drone or not in a category, ignoring download.
We know that it was grabbed by SAB, given the previous message, but the retry of the download causes SAB to issue a new ID and drone didn’t pick it up properly.
@Taloth Looks like the new ID isn’t picked up during the retry, I’ve seen this twice myself in the last week or so, but haven’t looked into it. Looking at the code its either taking SAB 1.5 seconds to update the ID, drone is unable to find it by name or something else.
To be clear, in my sab history I only have the original failed true blood episode download mentioned above. There was never an attempt by nzbdrone to grab another one or an attempt by sab to download another one.
Wasn’t sure if you were thinking that sab was in fact downloading a replacement but nzbdrone wasn’t communicating with it when it landed.