-
-
Notifications
You must be signed in to change notification settings - Fork 143
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
[BUG] <title>Search function not working #302
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Not a container issue, seek support from sonarr directly. |
well, my buddy uses unraid and has verified that the binhex version for arch works perfectly without any of these issues. I also spun up my windows install and the windows version works perfectly as well. for the giggles, i installed the Hotio version, and once again there are no issues. The issue is with your container not sonarr |
The issue is due to a badly crafted torrent file, which you can only replicate with the same indexers/custom formats and blocklists. |
Restoring the exact same backup on the Hotio install does not produce this issue. Searching prowlarr directly produces the correct results in a timely manner. |
Don't know what else to tell you. That error is caused by a malformed torrent file (prowlarr doesn't necessarily check this) |
so literally checking the same show on the Hotio, Windows and Binhex installs, all running from the exact same backup, somehow means there is a malformed torrent file that is causing the issue only on your container? Really starting to make sense why everyone tells me to avoid the linuxserver containers. |
Get us something we can reproduce this issue with. I can not see how this is a container issue, without having concrete path to troubleshoot. I researched online, and everything points towards a malformed torrent file. Have you verified from the logs, that the other installs also gets the same release from the same indexer? |
The search function on other installs applies my tags correctly doing the automatic search and ACTUALLY DOWNLOADS A TORRENT. Interactive search pulls the results instantly and i dont have a log filled with a search for each individual episode before the results appear and guess what? WHEN I PRESS DOWNLOAD IT DOWNLOADS. what else could i possibly provide that isnt already in my ticket? my install is as vanilla as you can get, its ported through Glutun using prowlarr 1337x, nyaa, tpb +Flaresolvrr |
Thats far from a vanilla setup. But post tracelogs here if you don't want to report report this upstream where it belongs. |
As a side note, the only other thing I can think of is portainer potentially messing with the container creation. If you're willing, could you try creating the container with compose? |
That seems to be a fix, none of the issues I've listed occur when I install through compose and restore the same backup, but when i install as a container and restore the exact same backup the issues are still the same. going through the settings everything is identical post install. |
Now take that back 😜 |
The issue can be reproduced easily by grabbing the same exact This is not a LSIO nor a Prowlarr issue, just corrupted torrent files generated by a 3rd-party service. I pushed a change to Prowlarr to report it's an |
everything marked [Info] is an interactive search not an automatic search. all of the errors before [Info] are from the automatic search. That said, im gonna move this issue over to Sonarr. After reviewing my interactive results for multiple different types of installs The Witch and the Beast pulls a large number of extra results that are not related, but the correct results in the previous version. Solo Leveling yields 0 search results again plenty of correct results in the previous version. Im also noticing issues with results for a few other Anime as well, once again all good prev ver. This may also be why the latest Radarr downloaded Liar Liar instead of Princess Mononoke. im not showing any of the same info in the logs btw, so yall seem to have all the extra logs, kudos, im just gonna stay a version behind and prolly roll back my radarr as well. |
This is not first report on this specific issue that I've seen. You can move it to any other repository you want, but the issue remains that monotorrent fails to validate the torrent file due to being invalid. Checking the logs in Prowlarr will confirm this based on the stacktrace.
|
I don't know what else to say other than in 4.0.9.2244 the error does not exist. i press search and it automatically grabs the correct files, i press interactive search and i get the correct results. 4.0.10(this is hotio not linux server sorry, but im sure they will be the same) |
The issue you're experiencing is something portainer is breaking and not the first time we've seen it with web based container management software: https://info.linuxserver.io/issues/2023-05-22-portainer/ |
https://privatebin.net/?50df342b005398eb#ErgqAeS9fhGSviWNNB2U2UgZbkkSkDc5RhRp9qWLXSMK Feel free to grab the torrent from itorrents from within my trace logs and attempt to import it in your download client manually.
You really seems focused on Sonarr for some reason on how it decides to pick which torrent to grab, when the issue is MonoTorrent throwing an exception in Prowlarr due to a bad torrent file. Disclaimer: I'm an active arr developer and contributor. |
few things, like the link above said, I needed to setup from scratch in order to get it all working correctly again, but after messing with things for a bit, found how to make it work for others without losing all of the settings. at least once i got it all updated the interactive search now shows correctly, results load quickly, it searches for what it is supposed to, tags apply correctly in the auto search and the gui correctly shows that there was an error adding it to the client and what the error is. the issue that alot of you are hung up on is the auto search errors, which is not what i was concerned about, but fyi those were related to nyaa not working, passed it through flaresolvrr and that seems to have cleared up that issue. im used to things erroring right away and not working for tests if it requires flaresolverr. all the errors i was actually concerned about (tags applying, interactive search issues, not adding to client) persisted even after fixing nyaa. while it did originally seem to only affect anime, i did end up discovering that more obsucure shows were also having the issue of loading every torrent in history in the search results. to j0nnymoe, sorry for the thumbs down, I did not realize i thumbsed down until i hopped on to share my findings today(this is why i dont use my phone for things), that was supposed to be a thumbs up cause the info in the link made enough sense to move forward. pretty much spent the last 2 weeks trying to replicate what was happening and how to ensure i dont lose everything when sonarr updates and im fairly confident this is the best way to ensure you dont need to start from scratch every update in portainer:
|
Is there an existing issue for this?
Current Behavior
Version 4.0.10
does not search correctly or apply tags.
Upgraded through Portainer 2.21.4
When using interactive search it searches first for the season then searches each individual episode in the series, logs show that it is searching and not interactive searching. When the interactive search finally loads you are unable to add any of the items, it will say it does, but nothing happens, this error seems to show up when doing that error code="500" description="Memory stream is not expandable."(I have 16GB of ram in the machine running it and also tried increasing to 32
Downgrading to 4.0.9 resolved the issue
Expected Behavior
No response
Steps To Reproduce
Upgrade 4.0.9 to 4.0.10
Search or interactive search
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: