I’ve done some troubleshooting on this and now I’m to the point where I wanted to see if anyone else is having an issue. What happens is NZBDrone grabs an nzb and sends it to sabnzbd, it happens with NZBGet as well, then the download fails stating not enough blocks. I’m running the most current version of both download clients. If the same nzb file is manually grabbed from the same indexer the file downloads okay. Last night I happened to be watching when a download failed. The nzb file was 3 minutes old when it was added to the queue. If failed 1m42s later. I was already logged in to the indexer from which NZBDrone grabbed the nzb and immediately manually downloaded the same nzb file. This time the file downloaded in NZBGet just fine. This only seems to happen with two indexers, omgwtfnzbs and one which can’t be named without risking a permaban. Members of the site will know which one I’m referring to. I have three other indexers configured that are working okay. This doesn’t happen every time NZBDrone grabs an nzb from the two affected sites but it happens to 1 in 3 grabs.
What newsgroup provider are you using? I’ve heard of similar issues with Supernews when its slow at getting articles from other providers. If the indexer is really fast at grabbing releases and drone checks right after its been updated (or relatively quickly) its possible the provider doesn’t have the files yet so it fails.
Sounds like the same issue as this thread: http://forums.nzbdrone.com/discussion/comment/1688 - as stated there, been really happy with Astra + blocknews and drone has a referral link with Astra (so hook us up if you go that route).
I have an unlimited account with and block accounts with and . The failed downloads do pull from the block accounts but the downloads still fail. If I click Retry in sabnzbd it retries but still fails. I have to delete the failed download and then manually download the nzb for the download to process successfully. This made me wonder if it was possibly a malformed nzb being transferred to the download client. I haven’t had any issues until recently and I even had the old version of NZBDrone set to RSS Sync every 7 minutes which got me the nzb’s just as quickly as I get them now.
I tried last year but the speeds were to inconsistent for me.
It sounds similar to what shedrock experienced as it’s with new releases but my issues started around the end of August.
Like I said I’m kind of stumped at this point and like shedrock I’m going mental as well.
Does sound like incomplete nzbs. I’d suggest having SAB store the NZBs it downloads (it will zip them up) and then when this happens again, before you redownload it, copy the already imported nzb somewhere (so it doesn’t get overwritten) and then compare the two nzbs. NZBs are just XML and any file compare tool should be able to compare them easily.
Currently drone just sends the URL to SAB and SAB downloads it. What version of SAB are you using?
I’m running SAB 0.7.16 and NZBGet 12.0-r860. I don’t run them at the same time I go back and forth for testing.
One thing I forgot to mention is that the site which shall not be named started using X-DNZB headers a while back. Do you think that could cause any issues? The guys at dog said that NZBGet was setup to use that kind of header which is why I tried it out.
X-DNZB just give more information back to the application hitting the site to look for nzbs or downloading them, if the client doesn’t support them they’re ignored, usually they’re used to tell the application how big the files that the NZB points to are, the category as well as API limits (from my experience with them).
I see the same on usenetserver , Its a propagation problem where the indexer is grabbing the nzb before it has a chance to get on your server.
What I did was change the interval time from the default 15 min to 30 mins and I am having a 95% better success rate as there seems to be more time before V2 grabs it.
I decided to disable the two indexers that are causing the problem and run just the other three for a while. The last time I did that I didn’t have any issues with incompletes but I do hate losing the two indexers. We’ll see how it works this time.
firstly i have not read every comment as i am feeling lazy today
however when i say you said missing articles it made me think of Incomplete or Fake Posts this was running rampant on Indexers for several weeks at one point but it seems to have settled down a bit now some of the more dedicated Indexers have implemented scanning techniques or User Generated ways of detecting password, or fake files
however especially on files that are on certain cable networks and after a certain period of time like even a couple days especially with popular shows these can quickly disappear
it is funny how much everyone cared about 1000+ days retention about a year or so ago and now we are lucky if we get a week for stuff before it is removed by DMCA
I don’t blame you for not reading all the comments as I was rather long winded today.
The CliffsNotes version is it’s happening with new nzbs that are only a few minutes old and if I immediately grab the same nzb from the same indexer the file downloads okay. On top of that I’ve only noticed it happening with nzbs grabbed from omgwtfnzbs and an indexer that can’t be named without risking a permaban.
You hit the nail on the head with regards to retention. Now 7 day retention would almost be enough.
