-
Notifications
You must be signed in to change notification settings - Fork 356
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
500 Error #306
Comments
Same here |
I'm looking in to it now - hope to have it back up soon |
Back up and running |
@henningsmith yay thanks! |
Great, thank you! |
Hi, I'm sorry, but this just happened again. Got a 500: Internal Server Error from the API and the demo page. |
I restarted the services again, but it seems someone is running a lot of queries against the system continuously. |
Internal server error is usually a problem with the backend code. I never seen such error raised because of high load. Is there a traceback available ? |
There were 2 separate types of errors today:
and
|
Hi, sorry to bother, but there is another 500 server error. Many thanks! |
Was the _start_new_thread error again... |
The proof of the pudding is in the eating. That sentence shows my lack of experience with high loads.
I will look into the traceback from #306 (comment) both seem familiar and related to high concurrency, possibly a mis-configuration related to how the flask application is running. In the the documentation build process, it is noted that the application can be run with: python conceptnet_web/api.py
cat /proc/cpuinfo | grep processor | wc -l
Edit: Production use uwsgi as show in the traceback. Sorry for the noise. |
InternalServerError: 500 Internal Server Error: The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application. |
Sorry, I ran too many queries last Wednesday! |
Unfortunately, it seems to be having the same issues again, any queries I made have the same error: "details': 'Internal server error', 'status': 500" |
Hi, I'm afraid the API is down. It returns a 500 error.
The text was updated successfully, but these errors were encountered: