-
Notifications
You must be signed in to change notification settings - Fork 1
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
constant scanning of same directory #2
Comments
I am running into a similar problem with the return code of 500. For me, it's for any directory that a-train picks up but autoscan is unfamiliar with. However, when pointed to autoscan-adapter, it gets hung in an endless loop of "not all targets are available, retrying in 15 seconds" and then "500 internal server error" Here is what autoscan is reporting
That last line repeats every 15 seconds. If another item comes down, autoscan never gets to it because adapter keeps giving it 500 errors
It will then go into the previous loop of retrying / error 500. Here is what autoscan-adapter is showing
If I go back to 0.0.4, autoscan-adapter reports similar findings, but autoscan just keeps going to the next item.
autoscan-adapter
since A-train doesn't currently, and probably won't ever give us exclusion options, it would be nice if autoscan or autoscan-adapter did. Thanks for writing this - I don't know of anyone else that had come up with a solution for Plex not refreshing the metadata on new files. |
so what i did is just roll back to the previous version of 0.0.4 until someone from autoscan-adaptor replies with a fix. if using docker-compose you can do |
I'm getting this issue only with Lidarr. When Lidarr connects to autoscan the errors start. If I disconnect lidarr from autoscan then everything is fine. From my rudimentary debugging skills I'm assuming Lidarr is not supported when autoscan-adapter is enabled |
Hi all, Looks like the refactoring I've made following some recommendations triggered this issue. I didn't have time to debug it but I'll do it eventually. For now just continue using 0.0.4 Also
This could be a bug in autoscan, which doesn't have a max retry option when failure occurs. |
Null pointer was rasied when scanning for a directory that didn't exist in Plex Fixed by handling the null pointer and returning an OK response (200)
The issue should be solved in https://github.com/dantebarba/autoscan-adapter/releases/tag/0.1.1. You can use the I'd recommend using the |
Awesome! Going to test this out now. Thanks! |
So far everything seems to working however I am seeing a bunch of this in logs
Not sure where the IP's are coming from but they are different IP's everytime EDIT: setup portscan blocker and now the IP's are gone. Logs were just showing random bots running port scans on online servers |
Ok closing! |
So I opened this issue Cloudbox/autoscan#202 up on autoscan thinking it was autoscan, however disabling autoscan-adaptor in my config gets rid of the internal 500 error and fixes the issue. I believe it has something to do with spaces in the url and the update that was pushed a few days ago as thats when my issue started
Request failed request_url=https://
<redacted>
/triggers/manual?dir=%2Fhome%2Fjohnfawkes%2FMergerFS%2Fmovies-4k%2FThe+Inspection+%282022%29 response_status=500the directory here is supposed to be /home/johnfawkes/MergerFS/The Inspection (2022) This is using TRASH naming scheme. Went back to version 0.0.4 using the tag in docker for now until solved. Thanks for making adapter. Loving it for bazarr and to trigger intro detection when autoscan scans items in plex
The text was updated successfully, but these errors were encountered: