Failed download handling issue from Sonarr
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
Hmm, interesting.
Yeah, shypike what are your ideas here?
Yeah, shypike what are your ideas here?
Re: Failed download handling issue from Sonarr
I'll have a look at improviseren logging.
Very likely a timing issue that only occurs in some situations.
Very likely a timing issue that only occurs in some situations.
Re: Failed download handling issue from Sonarr
Don't think it's a timing issue looking at his logs, there are minutes between sabnzbd declaring the job failed and Sonarr sending the delete request..
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: Failed download handling issue from Sonarr
So what is going on?
Is the job already gone before deletion?
Is the job gone after Sonarr sends the deletion command?
Does Sonarr send the wrong nzo_id code?
Is the job already gone before deletion?
Is the job gone after Sonarr sends the deletion command?
Does Sonarr send the wrong nzo_id code?
Re: Failed download handling issue from Sonarr
Sonarr sends the right code (see log), the job is there, but the problem is that it stays there.
Even though the Delete command is send (see his screenshot that still has the 1 Failed download in it).
The download gets added 3 times, fails the first 2 times. Sonarr sends 2 delete commands. Only 1 seems to have executed, causing the history to show 1 failed and the final succeeded download.
Even though the Delete command is send (see his screenshot that still has the 1 Failed download in it).
The download gets added 3 times, fails the first 2 times. Sonarr sends 2 delete commands. Only 1 seems to have executed, causing the history to show 1 failed and the final succeeded download.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
Exactly what safihre said.
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
Shypike, do we have any progress on this?
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
Just a gentle follow-up on this please?
Re: Failed download handling issue from Sonarr
Unfortunately we have no clue and can't reproduce it on our systems and with other users..
But we really should add the extra Debug logging on a delete command.
But we really should add the extra Debug logging on a delete command.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
Ok. Yeah, how soon can you implement that though? I would be happy to recreate the issue on my end when a more verbose debugging is incorporate in Sab. This issue is something that happens very often (not consistent) that makes it already annoying.
Re: Failed download handling issue from Sonarr
From what I have been able to reconstruct from the logging posted some time ago is this.
Sonarr tries to delete a job while it's being post-processed.
That:
1) leads to an (otherwise innocent) log entry and an error message
2) results in a job that is not deleted, because the actual post processing isn't aware of the delete command
Any idea why Sonarr would want to delete a job that is still being actively post-processed?
Sonarr tries to delete a job while it's being post-processed.
That:
1) leads to an (otherwise innocent) log entry and an error message
2) results in a job that is not deleted, because the actual post processing isn't aware of the delete command
Any idea why Sonarr would want to delete a job that is still being actively post-processed?
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
These jobs aren't completed at all so I'm not sure if post-processing even started? Sonarr tries to deleted these jobs because they failed for whatever reason (abort due to incomplete files, missing par files, etc.).
Re: Failed download handling issue from Sonarr
Yes, but I clearly see that the delete command comes
during the post-processing phase.
It could still be a race-condition.
About a half a second before PP ends, the status gets its final value.
So maybe that explains what happens.
I will look into counter-measures for this issue.
Removing the error message and log is the easy part.
What you want is that the item is still deleted.
In principle the running PP item cannot be stopped,
but this is an edge case, I think.
during the post-processing phase.
It could still be a race-condition.
About a half a second before PP ends, the status gets its final value.
So maybe that explains what happens.
I will look into counter-measures for this issue.
Removing the error message and log is the easy part.
What you want is that the item is still deleted.
In principle the running PP item cannot be stopped,
but this is an edge case, I think.
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
Oh ok. I thought PP only happens for completed jobs? Why would it ran PP for incomplete jobs?
Re: Failed download handling issue from Sonarr
Often failure can only be concluded by running the par2 verification.
That's done by post-processing.
Looking at the code, the delete action contains some awkward code.
I'm working on a better solution that will prevent this issue.
That's done by post-processing.
Looking at the code, the delete action contains some awkward code.
I'm working on a better solution that will prevent this issue.