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
Failed download handling issue from Sonarr
This is a continuation of this issue: http://forums.sabnzbd.org/viewtopic.php?f=2&t=17599
And here's my post on Sonarr's side: https://forums.sonarr.tv/t/failed-downl ... lem/955/69
Here's the excerpt of the logs from Sonarr:
15-10-29 13:32:18.3|Debug|SabnzbdProxy|Url: http://localhost:8080/api?mode=history& ... utput=json
15-10-29 13:32:18.4|Trace|SabnzbdProxy|Response: {"status":true}
15-10-29 20:21:13.7|Debug|SabnzbdProxy|Url: http://localhost:8080/api?mode=history& ... utput=json
15-10-29 20:21:13.8|Trace|SabnzbdProxy|Response: {"status":true}
It seems that Sonarr tried to delete the failed download and SAB responded with a Status:True which in reality is not the case as the failed download is still in the history of SAB.
By the way, this also happens with CouchPotato so it's more than probable that the problem is on SAB itself.
Any thoughts?
And here's my post on Sonarr's side: https://forums.sonarr.tv/t/failed-downl ... lem/955/69
Here's the excerpt of the logs from Sonarr:
15-10-29 13:32:18.3|Debug|SabnzbdProxy|Url: http://localhost:8080/api?mode=history& ... utput=json
15-10-29 13:32:18.4|Trace|SabnzbdProxy|Response: {"status":true}
15-10-29 20:21:13.7|Debug|SabnzbdProxy|Url: http://localhost:8080/api?mode=history& ... utput=json
15-10-29 20:21:13.8|Trace|SabnzbdProxy|Response: {"status":true}
It seems that Sonarr tried to delete the failed download and SAB responded with a Status:True which in reality is not the case as the failed download is still in the history of SAB.
By the way, this also happens with CouchPotato so it's more than probable that the problem is on SAB itself.
Any thoughts?
Re: Failed download handling issue from Sonarr
Have you tried 0.8.0beta1?
We won't be solving any problem in 0.7.20
We won't be solving any problem in 0.7.20
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
Not yet, I'll try that then. Are there no options in the interface to have SAB automatically update to beta builds?shypike wrote:Have you tried 0.8.0beta1?
We won't be solving any problem in 0.7.20
Re: Failed download handling issue from Sonarr
No, we support too many platforms to create a universal solution.kevindd992002 wrote:Are there no options in the interface to have SAB automatically update to beta builds?
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
So I'm using the latest version of SAB (1.0) and I still get this problem randomly. Again, the error is "Failed to remove nzo from postproc queue (id) SABnzbd_nzo_l4tau6". And as troubleshooted before, it is clear that Sonarr was able to send the command to delete the failed download from the queue but SAB is the one having the failed attempt to delete it from the queue.
Re: Failed download handling issue from Sonarr
Do you happen to have the relevant SABnzbd debug logging of the event?
Or can you create it?
Or can you create it?
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
Can I just simply click "show logging" and give you the file that I get from there? My logging level is set to "+Debug" from the beginning anyway (is this practice fine or should just keep at errors/warning?).
I can never recreate this issue. It is happening randomly but mostly when a whole season (multiple episodes) is being downloaded by SAB/Sonarr. This is true for series like Daredevil, House of Cards, etc. wherein they all give all the episodes of one season in one go.
I can never recreate this issue. It is happening randomly but mostly when a whole season (multiple episodes) is being downloaded by SAB/Sonarr. This is true for series like Daredevil, House of Cards, etc. wherein they all give all the episodes of one season in one go.
Re: Failed download handling issue from Sonarr
If you can download the log, just after the warning appears, that would be nice.
Please email to [email protected]
Please email to [email protected]
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
Looks like some race condition.
Should be fixable in 1.0.1
Should be fixable in 1.0.1
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
Yup which was the original possible cause when this thread was started. Is there an ETA to 1.0.1?
Re: Failed download handling issue from Sonarr
When we manage to solve the OSX El Capitan issue (doesn't start for some people unless they disable GateKeeper).
Tricky now that 10.11.4 has just been released.
Tricky now that 10.11.4 has just been released.
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
Ok, sounds good. Thanks!
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
I understand about the race condition and is probably due to multiple downloads but I'm having this same issue with just a single download.
Sab but Sab sees the sample release as "aborted, cannot be completed" this time around. Sonarr detects this as a failed download, gets automatically removed and blacklisted from Sonarr's queue but it remains in Sab's history. I've tried it twice already with the same results. This seems to be the problem on the old thread that I posted here. Here are the trace logs:
Sonarr: https://www.dropbox.com/s/le73zf0af06x6 ... r.zip?dl=0
Sab: https://www.dropbox.com/s/4cyw51h4f4skz ... d.log?dl=0
The release name is "Scorpion.S02E21.1080p.HDTV.X264-DIMENSION-Obfuscated"
Sab but Sab sees the sample release as "aborted, cannot be completed" this time around. Sonarr detects this as a failed download, gets automatically removed and blacklisted from Sonarr's queue but it remains in Sab's history. I've tried it twice already with the same results. This seems to be the problem on the old thread that I posted here. Here are the trace logs:
Sonarr: https://www.dropbox.com/s/le73zf0af06x6 ... r.zip?dl=0
Sab: https://www.dropbox.com/s/4cyw51h4f4skz ... d.log?dl=0
The release name is "Scorpion.S02E21.1080p.HDTV.X264-DIMENSION-Obfuscated"
-
- Full Member
- Posts: 211
- Joined: October 31st, 2012, 9:35 pm
Re: Failed download handling issue from Sonarr
There's a specific log entry saying this:
2016-03-30 08:08:28,153::INFO::[misc:1283] Cannot remove folder \?\D:\raw\Default\Scorpion.S02E21.1080p.HDTV.X264-DIMENSION-Obfuscate__ADMIN__
What could be causing this error?
I also don't understand why that log is pointing to the "D:\raw\Default" folder. That folder is my temporary download folder set in Sab. I have a "TV" category set that has a folder path of "D:\raw\TV" and Sonarr is pointing to that category. As I understand, if a download in Sab is set to the TV category, it's temporary download folder would be whatever folder path set for that category and in this case "D:\raw\TV", correct?
Is the default logging level of Sab set to "errors/warning" only?
2016-03-30 08:08:28,153::INFO::[misc:1283] Cannot remove folder \?\D:\raw\Default\Scorpion.S02E21.1080p.HDTV.X264-DIMENSION-Obfuscate__ADMIN__
What could be causing this error?
I also don't understand why that log is pointing to the "D:\raw\Default" folder. That folder is my temporary download folder set in Sab. I have a "TV" category set that has a folder path of "D:\raw\TV" and Sonarr is pointing to that category. As I understand, if a download in Sab is set to the TV category, it's temporary download folder would be whatever folder path set for that category and in this case "D:\raw\TV", correct?
Is the default logging level of Sab set to "errors/warning" only?