Support Forum

>>The next 0.6.0 Beta will not send NZB to history because of indexer limits That would make everything easier, thank you. >> thin. Maybe. But imagine that, eventually, the need for API change happens. Errors in the providers are actually making it more frequent. There's a great chance the users wil...

Feature: When changing provider API key on config, parse/update URLs of jobs in history that are failed. (Probably at queue too?). Why? - You have failed jobs in your history that you waited a couple hours / day to try again (daily limit, etc). You know they are valid anyway. - Meanwhile you were as...

No, they look ok so far (could not check them all, looked at like 50 of them and didn't find anything unusual. Is this situation possible: - sabnzbd had the "Detect Duplicate" option set as ignore. - Jobs got orphaned in the download folder after failed / poorly done upgrades, cleared queu...

Hi Shypike, thank you so much for helping. I'm lost here. I found out dozens of directories with this situation: Like 50 files .rar and the files with the same exact name but named .rar.1...I hadn't considered par2 as the source of the .1 (as to avoid overwrite of original file). I will try to test ...

I have a lot of directories in my system which I don't know if were processed or not. They accumulate to more than 200 every week or so. Checking each of them manually takes a ridiculous amount of time. I wrote a script to go in each directory, find par, rar, sfv, srr, srs, etc and try to do somethi...

Got it, thank you!

What characteristics define a job as "orphaned" so that it goes to the job list at "Status/Queue repair"? A have more of these than I count and check one-by-one. I mean, did they fail to download, were duplicates of other stuff already upper in the queue so not downloaded, downlo...

Ah ok, I was thinking large (server, power desktop) and not the other way around (NAS)... Now I see, you are absolutely right. Running sabnzbd on a Nintendo DS, a coffee machine or something must create such results. I was about to ask you if you own a Usenet Host LOL :) You know what, I think unrar...

I've never seen anything like this with an average of 5TB/day downloaded and processed. I Can't imagine what kind of operation your running there :) Out of curiosity what size of download can take 12 hours on unrar + par2 r processes? Honestly, I am pretty sure that if I establish something like Max...

Yeah, nzbmatrix and nzb.su too. We know its not a 404, 500, etc error because there's content with the API and Error in the string. But that's it. Both providers are absolutely defaults for Sick Beard users. All we can know is date/time when the download attempt failed. I think it could be archived ...

It'ss a good idea. I've been also thinking about an option to set "max par2 processing time" / "max unrar processing time" settings in the config. We know our systems. We know what is a reasonable time and what is not. And, obviously, the average lumberjack joe would have the opt...

sabnzbd+ fills history with one hundred "URL Fetching failed: Unuzable nzb file". Visiting the URL you see it actually is one of your search providers telling you your "API daily/hourly limit is reached, try again later". - Deleting this items from history would confuse the nzb s...

There is a setting in sabnzbd+ to stop downloading while files are being post-processed .. maybe that is an option ? Yes, it has always been unset, so sabnzbd+ could download during post-process if it wanted to. Checking it seems unproductive (idle bandwidth, cpu, etc). All the server is supposed t...

Ok, so I Googled a little and found out Sabnzbd actually does try to fetch more blocks when repair fails. This is news to me. I don't know why it never happened/worked here. I have other post at this same forums asking if there wasn't a way to automatically download more par2 files when needed... I'...

Hi, I'm not sure if what I am about to describe here is actually a problem, a new sabnzbd normal  behavior for the latest Beta or if it has always been like this, so excuse me. I have never seen this happen. 1) I only noticed because I receive e-mail from system to root saying CPU/RAM was dying. Wen...