Failed downloaded amiss

Help & Support
1

Using nzbdrone 2.0.0.1988, just updated, but have noticed this over the past week or so.

Sabnzbd ver 0.7.18

Drone saw and requested an eps, it was handed off to sabnzbd

SAB downloaded but is unable to repair so its sitting with a repair failed message.

At this point Drone sees this as an eps that is in queue but also as a failed download (per calendar info when I hover over the eps in calander )

My options in Drone for failed downloads are

enabled yes
redownload yes
remove yes
Grace Period 2
retry interval 60
retry count 10

Seems to get stuck here.

I’m just wondering when the failed download is removed? After all retry counts/interval has expired?

I just reread the FAQ, Guess I’m curious why its still in queue and failed??

2

In drone’s history, how old was the file when it was grabbed?

Which version of drone are you running?

3

I just updated, so it was the dev release prior to 2,0 0 1988

It was yesterdays Real Time with Bill Maher

I have already deleted the fail from sab, which cleared it in Drone. Then did another auto search and it d/l fine. Guess this might indicate a need to delay the grab.

So any delay will need to be in the profile associated with the series. ??

4

Yes.

This sounds like an issue with retrying though, SAB doesn’t report the new ID when the release is retried and drone loses track of it, though it should log an error to that effect.

5

we really should ask sab to fix it.

6

Sorry I will try to be prepared to provide better info, but its not really everyday issue. But I have seen it 2 or 3 times in the past few weeks I was just trying to get a better understanding of what was happening between drone and sab.

Having already massaged drone and sab thru this, just wanted to say thanks to those that responded.

7

I’ve seen it as well (with an older version of SAB), so I just upgraded to 0.7.18, not too hopeful given you also have issues with 0.7.18.

@Taloth yes we should, to confirm this is when we rety and the ID changes when it goes from History back to the Queue?

8

it happens on the retry api call, when the item gets moved back to the Queue.

Something similar happens when ‘Check before download’ is enabled, but afaik the sab team recommends not using that one anymore.

9

Just checked, disable on my setup.

10

I know, drone warns if it’s on. I was just pointing it out to markus so he knows the two situations that sab creates a new id.

11

Im having this same issue. Usually only happens on one or two episodes but tonight I had six. Is there anything I can do other than wait for a fix from sabnzbd? Does nzbget have this issue? Episodes are usually 0.2 or 0.3 hrs old when grabbed. Im on drone version 2.0.0.2003 and sabnzbd 0.7.18

12

You can disable retrying for failed download handling, but that would just blacklist them straight away and the propagation issues last night are the reason it was added.

No, get shouldn’t have this particular issue.

13

I also had an issue like this i am using sab 0.7.18 and yesterday it attempted to download two episodes one for The Mindy Project and the other for Bad Education they failed and sat in the history overnight without being retried (as far as i know)

and today Hell’s kitchen failed (most likely propagation issue) and sat there for about 5-6 hours and nothing changed eventually i manually searched for them because i wanted to watch the shows

all my failed download handling settings are default

I am using the torrents branch right now

not glad it happened but glad you guys are aware of it

14

Not sure its helping but I finally added an hour or 2 delay. But it might be masking another issue between Drone and Sab talking to each other. I think Markus101 had asked about the age when grabbed and I found that the ones that caught my eye were rather fresh, .2 to maybe .3 hours old… Keeping that in mind, I have noticed most of my latest grabs have been over an hour…

15

There were major propagation issues yesterday, most of my grabs were hours old before drone even saw them on my indexers.