New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[sabnzbd develop branch] spotweb gives error when pushing to sabnzbd #1501
Comments
You have 79 Tracebacks in your log! Shouldn't you solve that first?
Disk / rights problem?
more disk problems ... |
I did make a change to the API, the output has changed slightly.
|
@sanderjo Those were from yesterday, I solved those yesterday. The entries with today's date don't have any tracebacks, I did check those. I checked the downloads I did today via spotweb and there I didn't see any tracebacks, neither when I scrolled through all today's logs. |
@Safihre The screenshots here is from after I tried download the same download via radarr, hence you not seeing a download arrow with a red cross in it. |
The change I made is this: |
In which commit id did you remove that? I could try undoing that commit and then seeing how spotweb reacts before that commit in the develop branch. |
When I switch to the previous commit it works as expected
|
While annoying, I do want to use this major release to including breaking changes. Otherwise it might be another 8 years 🤔 |
looks like spotnab sends |
and about the issue adding, spotnab uses output=text and then checks if 'ok' was returned they should just update to json and handle that.. as that will fix 3.x+ support and still work fine with 2.x and older as well |
Thanks for looking into that! |
Thanks! I created an issue for spotweb referring back to this one. |
@Safihre : Request types Supported output types are json, xml and text and can be specified in the request: |
Text is still supported, but it doesn't just output |
as a side note, this change also breaks the original sickbeard (as it also checked for 'ok'). which is one of the reasons why shy left this the way it was for so long original sb has been abandoned forever.. but there is a lot of people that still use it. those people really should move to one of the various sb forks that does get updated (checked those and they all use json output). |
Thanks to analysis of @thezoggy I've reported a bug report at Spotweb. |
This fix has now been pushed into master branch and released as version 1.4.6 as of yesterday. |
I am running the develop branch of sabnzbd, I just noticed today that when I login to spotweb and push an nzb to sabnzbd the green download error gets a red cross through it as if the pushing has failed. However sabnzbd does receive the nzb and it does start downloading, I tried it with other titles and I get the same result there.
I see this in the apache logs:
[Thu Jun 11 19:56:33.655419 2020] [php7:notice] [pid 6121] [client 0.0.0.0.29:33658] sabnzbd push : http returncode: 200 / / {'status': True, 'nzo_ids': ['SABnzbd_nzo_j4cmwk47']}\n, referer: https://spotweb.feedmebits.nl/?page=index&search[tree]=cat0_z0_a9&search[value][]=
In my sabnzbd logs I see sabnzbd receiving the file from spotweb and starting to download:
removed
Here is what I see in spotweb when I try it:
The really strange thing is when I add the download to sonarr/radarr and then request my searcher to look for it on my spotweb indexer I don't get any errors in de apache logs. When I then refresh spotweb it shows it correctly download the a green check mark.
I am using:
spotweb hasn't been updated in a few months:
So thinking it may have been one of the recent updates to the develop branch.
I don't log into spotweb very often since I use radarr and sonarr so I wouldn't be able to tell you since when this started.
The text was updated successfully, but these errors were encountered: