SABnzbd Forums

I set nzbdrone to enable its failed download handling so that it removes a failed download from the history of sab. At random times, sab gives me these error debug log: ERROR: Failed to remove nzo from postproc queue (id) SABnzbd_nzo_fj50g8

I tried asking the nzbdron forums about this and they say that it's a problem with sab so that's why I'm asking it here now.

Please help. Thanks.

Since I have no idea what NzbDrone is doing, I cannot really solve this.
I need a lot more info.

shypike wrote:Since I have no idea what NzbDrone is doing, I cannot really solve this.
I need a lot more info.

Can I let the admin of nzbdrone post here so that you guys can solve this?

Hey shypike,

NzbDrone is making a call to remove a failed download from SAB's history: It gets the NZO_ID by checking SAB's history.
It uses the API key OR username and password to authenticate (preferring the API key).

Let me know if you need any more information in regards to what NzbDrone is doing.

kevindd992002 wrote:At random times, sab gives me these error debug log: ERROR: Failed to remove nzo from postproc queue (id) SABnzbd_nzo_fj50g8

Is the job the removed? It's a bug if it's still there.
Otherwise it could be a timing problem.
If you hover the mouse cursor over the history entries, you can see the NZO-ID at the end of the URL.
(In Firefox, the history URLs are shown at the bottom of the Firefox Windows.

No, the job is not removed from the history. Every time I see a failed download in the history that is not removed, I see the same debug log. If it's a timing bug, how can we go about in fixing it?

It would only be a timing bug if the job was deleted after all.
So is the nzo_id that's being reported still in the queue?

shypike wrote:It would only be a timing bug if the job was deleted after all.
So is the nzo_id that's being reported still in the queue?

It is not being deleted for some but it is deleted for others. As I said it is intermittent.

It is not in the queue, it is in the history section when it fails downloading for whatever reason.

Weird, an intermittent failure when looking up an id in a simple table.
I'll have a look at this, but it's probably very hard to find.
Assuming it isn't platform dependent.
On which operating system does it all run?

shypike wrote:Weird, an intermittent failure when looking up an id in a simple table.
I'll have a look at this, but it's probably very hard to find.
Assuming it isn't platform dependent.
On which operating system does it all run?

Yes. It's running on Windows 7 x64.

Do you need any logs from me?

I noticed another weird behavior now. I was downloading an episode and it finished just fine but then it got deleted from the history?

What happened was the download failed at the first time because it needed more par files so sab automatically put it back to the queue and then downloaded the necessary par files. It was able to download them completely and it repaired the release. But then nzbdrone still recognized it as a "failed" download and then removed it from history. Why is that?

Markus, I hope you can give your ideas here.

Any updates here please?

I'm sorry, but errors caused by lack of cooperation between apps are very hard to debug.
I would need a lot more info, so a debug log would be nice.

shypike wrote:I'm sorry, but errors caused by lack of cooperation between apps are very hard to debug.
I would need a lot more info, so a debug log would be nice.

I understand but what debug info do you need? As I said on my previous reply the other day I would give any info that you want so as to solve this problem.

Re-reading your message gives me some thought.
NzbDrone mis-interprets what's going on in SABnzbd.
Now I don't know why that is, but can do some guesses.
Are you using folder renaming? (Config->Switches)
Other than that, did you ask this also on the NzbDrone forum?