I'm getting sporadic 500 errors using the search method. Is everything running 100%?
Un film, une émission télévisée ou un artiste est introuvable ? Connectez-vous afin de créer une nouvelle fiche.
Vous souhaitez évaluer ou ajouter cet élément à une liste ?
Pas encore membre ?
Réponse de Travis Bell
le 6 septembre 2014 à 01h15
Hi Kenton,
No known issues this evening. Is it possible you were hitting our rate limits?
Réponse de Kenton Glass
le 6 septembre 2014 à 03h59
I don't think so. I'm running a task in Ruby and delaying requests so I won't hit the rate limit. If I did, wouldn't I see a 503 response instead 500? It's very random when I get a 500. Once I got in on my second query, and then another time 50 or so in. This same code was working fine last weekend.
Réponse de Samara
le 6 septembre 2014 à 08h24
I've noticed this the last days using different apps, it's very annoying
Réponse de Travis Bell
le 6 septembre 2014 à 11h09
We're looking into this but there is nothing obvious at the moment. I'll update this thread when I have more information.
Réponse de Kenton Glass
le 6 septembre 2014 à 11h19
Thanks, Travis! Could it be related to the API update on 9/4?
Réponse de Travis Bell
le 6 septembre 2014 à 11h54
Hey Kenton,
We haven’t done a deploy on the API since Aug 28 (and there’s no obvious load issues), so we’re not sure what it could be quite yet.
Réponse de ranjhanisaddam
le 6 septembre 2014 à 14h17
I think the problem resides your side because sometimes this error comes and some times it does not...!
Réponse de Travis Bell
le 6 septembre 2014 à 18h09
Hey guys,
We’ve just deployed the fix for this, you can see our error rate has gone back down to zero: http://note.io/1lIaCSe
Weirdest thing, they did indeed start on September 3 but there was nothing done on our API infrastructure and it only seemed to affect 3 of our 8 HTTP servers. Solution? Restarted the app and everything calmed back down. Gotta love it when those gremlins get in there...
Réponse de Kenton Glass
le 6 septembre 2014 à 18h13
So lovely when a restart fixes weirdness. Thanks for looking into and fixing things on a Saturday, Travis!
Réponse de Michell Bak
le 14 septembre 2014 à 18h22
Hi there!
I'm getting some HTTP 500 errors tonight, so I thought I'd re-open. It might be because I'm hitting some limits, but I'm not sure since the API documentation might be a bit outdated in that area.
This says that we'll receive a 503 error if we exceed the request limit (of 30 requests every 10 seconds): http://docs.themoviedb.apiary.io/reference
While this says that we'll receive a 429 error if we exceed the request limit (of 40 requests); https://www.themoviedb.org/documentation/api/status-codes
Can we get some clarification on that? :-)
Réponse de Samara
le 14 septembre 2014 à 19h16
I'm getting this errors, too since this afternoon
Réponse de Travis Bell
le 14 septembre 2014 à 20h57
I just restarted the app like before, can you tell me if they have stopped?
Réponse de Samara
le 15 septembre 2014 à 19h45
seems to be okay
Réponse de Carlos G. Vallejo
le 22 mai 2017 à 13h50
Dear friends: today I have found this ugly error; the message error was:
If you try to go to
https://api.themoviedb.org/3/search/person?api_key=...&language=es&query=Brad&page=3
it appears an even ugglier error: in Firefox:
(I am writting from Spain). It's means "File not found" (File???)
This doesn't happens when I was looking at
https://api.themoviedb.org/3/search/person?api_key=...&language=es&query=Brad&page=2
or
https://api.themoviedb.org/3/search/person?api_key=...&language=es&query=Brad&page=4
The "language=es" is not the problem: it happens the same without it. It looks like the server doesn't like "Brad": the same code works well when asking for "Smith" or "e", with the expectable 429 error code after 40 queries.
I've ommited the api_key here, but not in the queries, of course.
Réponse de Travis Bell
le 23 mai 2017 à 11h06
@vallejo Would you mind creating a new discussion for this? No need to resurrect a 2.5 years old thread