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
Lost connection to MySQL server during query #467
Comments
Is this consistently reproducible for you? I doubt that this is an issue with CTFd considering that the error message is usually related to network issues. Another thing to note is that the cache clears out about every 5 minutes and given that CTFd wasn't being run for 15 minutes perhaps you entered some situation where the database was getting hammered due to too many configuration queries? Just a random hypothesis. |
Thank you for your response! I doubt that the database was under stress at the time of error. I also don't know if it can be a network issue, since the database is connected to the application through the local Docker network (if I understand correctly). Do you have any more information on the cache part? Would it for example help if I configured a redis server to help with Flask caching? I will test the platform again next monday and will report if the problem reoccurs. I will be monitoring the database more closely. |
CTFd uses caches to store database queries so that it doesn't need to constantly look up whether or not it's setup for example. By default CTFd will use an in memory dictionary to cache data so you can get away with not using redis. |
Environment:
What happened?
When adding a new challenge, I took some time to fill in the form. When sending it, I received an internal server error. I tried it again and it worked normally.
What did you expect to happen?
The challenge to be created normally.
How to reproduce your issue
Click the button to create a new challenge, fill in the form. Then, leave the page open for around 15 minutes and click the button.
Any associated stack traces or error logs
Error.log
Access.log
The following errors may also be related to the same issue:
Error.log
Access.log
Error.log
Access.log
access.log
error.log
The text was updated successfully, but these errors were encountered: