Just started using NZBDrone and it looks like a great product. The failed download handling is what particularly attracted me to the software and it works well.
I have a problem that sometimes a new release gets posted on a search provider before it is complete on my news provider, and NZBDrone gets in there and starts downloading it and the download fails because there are bits missing. Try again 10-30 minutes later and it’s fine. (I used to have the same problem with Sickbeard so it’s not specific to NZBdrone)
The trouble is, the release then gets blacklisted and so NZBdrone won’t try to pull it again.
Maybe there is already a solution to this problem, if so could you let me know? If not, what would be useful is to be able to
a) set a “minimum age” to a release before it gets blacklisted OR
b) a setting which allows for a release to be retried more than once before it is blacklisted, OR
c) some kind of minimum age setting so that NZBDRONE doesn’t try to grab any release younger than a certain age (e.g 30 minutes old)?
from what i have gathered from participating in several of these posts and discussing with @markus101 it is a propagation issue where the uploaders of the content are using a provider (i think easyusnet lately it used to be astraweb a lot) that their propagation process is slow and not very efficient so it takes longer than it used to for the files to spread out over the various usenet servers and indexers so when NzbDrone grabs a file thinking it is complete it is in fact not complete which it soon discovers and then treats it like a release that has been taken down for DMCA and blacklists it even though it could be as litle as an additional 15 minutes longer and the propagation could have completed and it would download perfectly fine
Which is why if you later on perform a manual search or clear the blacklist and search again it would find them
as @markus101 mentioned above a couple different plans have been proposed on trello to help combat this hopefully these can be implemented at some stage or the uploaders may switch to a better usenet service provider and that should hopefully solve the issue
@tymanthius said:
BTW, as a note on the propagation issues - a recent note in nzbget’s r66(?) development version they are adding an option to delay download.
This could greatly help w/ propagation issues as well.
that’s cool it made me wonder though if the Pause For function on sabnzbd might help with this then by default you can have it on pause for 6 hours however you can also specify longer by using the custom feature this would also mean figuring out that sweet spot between having propagation complete and not having episodes affected by DMCA which varies show to show