Failed / Retring beyond rety limit

Help & Support
1

Hi, I seem to have an issue with the retries on failed downloads…

I have retries set to 2

EG:

Defiance.S02E09.720p.HDTV.x264-IMMERSE

According to the emails from SAB this is the history

15/8 09:20 Failed
15/8 12:21 Failed
15/8 12:24 Failed
17/8 16:59 Failed
17/8 17:59 Failed
17/8 18:30 Changes to different release and COMPLETES
21/8 17:25 Failed IMMERSE release again
21/8 18:25 Failed
22/8 11:10 Failed
22/8 12:29 Failed
22/8 12:32 Failed
25/8 10:46 Failed

So it seems to be retrying way too many times.

Blacklist in drone:

Log in drone:

Pastebin of log:

http://pastebin.com/gvEDXqc

2

What is your retry interval? Also, your log has been removed, so we’re lacking quite some info here. The red blocks in the screenshot make perfect sense: the download that you sent to SAB at 10:42 failed at 10:46 according to the emails you say you received and NzbDrone picked this up at 10:47…

Keep in mind that this failed download handling only handles failing reports, so NZB files. It does not handle the same releases as far as I’m aware, and to be honest I wouldn’t want it to. Just because Defiance.S02E09.720p.HDTV.x264-IMMERSE fails when it’s posted to one group doesn’t mean it would fail when posted to another.

How is the episode marked in your episode list? I doubt Drone would keep adding it if it was already marked as successful there.

3

Thanks for your reply…

Retry is on 60min

The WEB-DL was successfully completed on 17th August.

This is the Activity for this ep:

if you over over the ‘i’ they all say the same:

If I do a manual search I see this:

All of the red symbols say:

Now I dont have drone set to remove failed downloads from SAB, so not sure if that is doing something crazy, just seems odd that it would do this for more than a week

4

Do you restart drone periodically? Or, hibernate/sleep… anything that might case drone to restart. Or lose the connection to sabnzbd.

5

No, Its on 24/7

Ok, its happenning with another release and with the new keeping of 50 log files it may be easier to see what is happeneing…

“New_Tricks.11x02.Tender_Loving_Care.720p_HDTV_x264-FoV”

Succesfully downloaded 26/8/14 09:47

since then drone has sent a ‘retry’ request to SAB 7 times for the same release:

This is the log of the most the second last time it tried:

This shows the times when Drone retried the release and failed … the green line is where it was successful (not im my email list)

6

The logs only show one retry by drone:

14-8-28 01:00:01.4|Info|FailedDownloadService|[New_Tricks.11x02.Tender_Loving_Care.720p_HDTV_x264-FoV] Download Failed, initiating retry attempt 1/2.

and it successfully getting the new ID from SAB:
14-8-28 01:00:07.9|Debug|FailedDownloadService|[New_Tricks.11x02.Tender_Loving_Care.720p_HDTV_x264-FoV] Changed id from 1-SABnzbd_nzo_cwjkvq to 1-SABnzbd_nzo_szucse.

Are there more retries in the logs?

7

Sure…

Here is the other one an hour later for the same day:

http://pastebin.com/62WUiinH

Unfortunately even with 50 log files being kept, I dont have the logs from the previous (days)

8

It retries a second time an hour later:

14-8-28 02:00:19.4|Info|FailedDownloadService|[New_Tricks.11x02.Tender_Loving_Care.720p_HDTV_x264-FoV] Download Failed, initiating retry attempt 2/2.

and finally stops retrying:

14-8-28 02:03:23.0|Info|FailedDownloadService|[New_Tricks.11x02.Tender_Loving_Care.720p_HDTV_x264-FoV] Download Failed, Retry limit reached.

Are there another events in drone saying it retried that release?

9

Yes there are from previous days like the image from a few posts up shows - I dont have the logs now, but I remember they say the same thing… usually it twice each day.

Just happened again:

http://pastebin.com/U8VSMV7Q

10

We need more context in the logs, can you just pick all the log files, zip em and PM them to us?

11

Logs are helpful:

14-8-28 16:03:49.8|Debug|NzbDrone.Update.exe|Starting NzbDrone Update Client
14-8-28 16:03:53.6|Info|Bootstrap|Starting NzbDrone - C:\ProgramData\NzbDrone\bin\NzbDrone.exe - Version 2.0.0.1878

14-8-28 16:03:58.4|Warn|FailedDownloadService|[New_Tricks.11x02.Tender_Loving_Care.720p_HDTV_x264-FoV] Download Failed, waiting for retry interval to expire.
14-8-28 17:04:50.7|Info|FailedDownloadService|[New_Tricks.11x02.Tender_Loving_Care.720p_HDTV_x264-FoV] Download Failed, initiating retry attempt 1/2.
14-8-28 18:05:37.8|Info|FailedDownloadService|[New_Tricks.11x02.Tender_Loving_Care.720p_HDTV_x264-FoV] Download Failed, initiating retry attempt 2/2.
14-8-28 18:08:48.8|Info|FailedDownloadService|[New_Tricks.11x02.Tender_Loving_Care.720p_HDTV_x264-FoV] Download Failed, Retry limit reached.

Yes, it is initiated after an auto-update. (hench my earlier question about restarts)

We only keep track of the retry count in memory, not in the database. This means of drone restarts during a ‘wait for retry’ period, it essentially resets the counter. That isn’t bad, coz we have plenty of hours per day that we don’t push new versions. Would only cause a few more retries at the most.
The problem was that we didn’t check the history to see if we marked the download failed, at least, not until after the retry logic was evaluated.

The reason why not more people are running into it is because they have ‘Remove’ enabled, so after finishing the retry sequence the sab history item gets removed by drone.

Anyway, I’ve push a fix.

12

aha, yes, I didn’t consider auto updates into the equation…

Superb work! Yourself and Markus… It was obvious from when I first started using Drone a few months ago what it can become, so I did donate a small amount after just using it for a few days!

THANKS GUYS :slight_smile: