-
-
Notifications
You must be signed in to change notification settings - Fork 95
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] Suppressing retries for 30 seconds #746
Comments
OMDb has a 1000 requests per day limit. If you go over that you get a connection time out. TMDb doesn't have a set limit. However, they do have rate limiting and if you go over the limit within a set period of time (e.g. lots of new requests for uncached items) then they will timeout the connection for a few minutes. Basically TMDb rate limiting is like a bucket with a hole in it. Every request you make adds water to the bucket. If you make too many requests in a set time it overflows (timeout) and you have to wait for it to drain. |
I'm sure I used ver few times of these API today, I manually tried the OMDB url in browser and could get the correct response each time. Based on the information from above stackoverflow thread, I checked the TMDB helper code, it does use response directly from requests module. Can you try to copy the response result and close the connection as soon as possible after using? I can test it first if you can make a test build. |
Can't see any harm in trying. Requests module is not meant to need to call Add a test build in this PR: #747 |
Thanks @jurialmunkey, I tried the test build for some time and didn't see any previous errors, but I can see the errors like the following, it's much less frequent though. These errors seems not to be related with TMDB/OMDB, as I'm on Xbox which is a restricted platform, not sure whether this may related with the python functionality on Xbox.
|
We could try bumping up the timeout a bit. I just pushed an update to that branch which bumps timeout to 15 seconds |
Same here (on 3 PC), getting this message every time I start Kodi or after episode ended (When the TV Progress list need to update). "ConnectionError: TraktAPI Timeout. Suppressing retries for 30 seconds."
Deleted everything (All cached), re-install, authorize-re authorize trakt, nothing help.
Yes please. |
I already did bump the time out. Anything now is the api refusing the connection because their server is busy or due to rate limiting. Trakt in particular has had issues of late with their servers. |
Thanks @jurialmunkey. Didn't see the update from the regular repo (still show 4.8.9 in kodi), updated from here 4.8.11. Yeah, I know about Trakt API issue. They did say "fixed it, added more servers etc." and other addons doesn't show this message (But they do takes 45-90 seconds to complete) so the message from TMDBHelper was a little confusing. :) Update: launch Kodi after couple of hours. The message return. Bummer. |
Hi @jurialmunkey, I always encounter the "Suppressing retries for 30 seconds" for TMDB and OMDB from TMDB helper. It happens very frequently. At first I thought it's the API usage limitation, but TMDB has no API limit, so I believe it's the add-on issue now.
From the information below, it seems it's due to the connection pool usage limit, can you check this? Thanks!
https://stackoverflow.com/questions/46188295/python-httpconnectionpool-failed-to-establish-a-new-connection-errno-11004-ge
The text was updated successfully, but these errors were encountered: