search

theotherp / nzbhydra2

Usenet meta search
Other
1.25k stars 75 forks source link

Sabnzbd says NZB was added successfully but didn't return an NZO ID #430

Closed GregSawin closed 4 years ago

GregSawin commented 5 years ago

I have my SabNZBD setup to track and prevent dupes. But this is stopping the +Sabnzbd bulk load within hydra, when it blocks a dupe.

So for example if I have 5 results and download # 3, via sabnzbd. Then I select all 5 and click +Sabnzbd, it'll add # 1, # 2 then throw an error "Sabnzbd says NZB was added successfully but didn't return an NZO ID". Checking sabnzbd I can see the "Ignoring duplicate NZB..." error for # 3. The state of nzbhydra2 at this point would be # 4 & # 5 are still checked. So I'm thinking I hit +Sabnzbd again, but I get the exact same error. Instead to proceed I must check and then uncheck # 3, then when I hit +Sabnzb the other 2 (# 4&5) will get added successfully.

Ideally I'd like the +Sabnzbd button to add all and not stop when it gets an error, perhaps listing at the end those that couldn't be successfully added, and keeping them checked in case I want to try again.

Alternatively fix the issue where # 3 shows as unchecked but actually is included on subsequent +Sabnzbd calls.

theotherp commented 5 years ago

Please follow the instructions when creating a new ticket and post your debug infos.

theotherp commented 5 years ago

Also, which option did you select in sabnzbd for duplicate NZBs?

GregSawin commented 5 years ago

Thanks for looking into this, I currently have Sab's 'Detect Duplicate Downloads' set to Discard. I also tried the fail job option but no change in hydra behavior.

I just repeated the issue with some random mp3's, there isn't much in the logs: 2019-09-04 10:40:03.360 INFO --- [0.0-5076-exec-2] org.nzbhydra.downloading.FileHandler : [Search: 322193, Host: Dragon] NZB download request for "Dim Key - Test Drive-DKNW127-SINGLE-WEB-2019-JUSTiFY" from indexer nzbplanet 2019-09-04 10:40:04.184 INFO --- [0.0-5076-exec-2] org.nzbhydra.downloading.FileHandler : [Search: 322193, Host: Dragon] NZB download from indexer successfully completed in 824ms 2019-09-04 10:40:04.186 DEBUG --- [0.0-5076-exec-2] o.n.downloading.DownloadStatusUpdater : [Search: 322193, Host: Dragon] DOWNLOAD_STATUS_UPDATE: Received download event. Will enable status updates for the next 360 minutes 2019-09-04 10:40:04.186 DEBUG --- [0.0-5076-exec-2] o.n.d.downloaders.sabnzbd.Sabnzbd : [Search: 322193, Host: Dragon] Uploading NZB Dim Key - Test Drive-DKNW127-SINGLE-WEB-2019-JUSTiFY to sabnzbd 2019-09-04 10:40:04.380 ERROR --- [0.0-5076-exec-2] o.n.downloading.downloaders.Downloader : [Search: 322193, Host: Dragon] Sabnzbd says NZB was added successfully but didn't return an NZO ID

One difference this time is that the selected item with that error remained selected. So technically to reproduce what I originally reported, you need to make at least 1 selection on another page of hydra results. In other words select 2 items on page one, the 1st being a duplicate, and you'll see the error and both remain checked. Building on that if I also check an item on page 2, then send to sab, both items on page 1 are now unchecked but still get submitted if I hit sab again. The page 2 item remains checked and not added to sab. So hydra sent the 1st to sab, got an error and stopped, the 2nd and 3rd non-duplicate items did not get sent.

I'm happy running other tests and/or extracting other log snippets but I'm not comfortable sending full logs, there's info in there I'd consider sensitive considering my github account is not anonymous.