Gunicorn [CRITICAL] WORKER TIMEOUT #468
Comments
As I mentioned in #467 I think this is primarily a network connectivity issue. IIRC, SQLAlchemy in CTFd attempts to keep a couple connections to the database alive. A disruption in network service that happens at the right time could cause some issues with CTFd itself and gunicorn. If you can find something that causes this to happen consistently, it would go a long way. Also how did you deploy this CTFd instance? |
I just deployed it using the docker-compose.yml file. You are probably right about the network connectivity issue. I will test again next monday and notify you of the results. |
Hi @FreakyFreddie did you find any way of solving this? I appear to have the same problem. I am also using this version of Ubuntu, doing it in an EC2 and using the docker-compose method to create two containers. @ColdHeat this is the issue I talking about on slack here. I followed the docker install instructions from here, the docker-compose instructions from here and the CTFd deploy instructions here When I run
|
In the meantime, I stopped using Docker and instead used the instructions here (thanks @ColdHeat Even though it using sqllite, it still seems to work okay so I will probably stick to that for now although it would be good if someone figured out why the docker option doesn't seem to work well. |
Environment:
What happened?
Seeing a lot of Gunicorn [CRITICAL] WORKER TIMEOUT entries in the error.log file. I do not fully understand what this means. I think it happened around the time the application stopped responding. I had to reboot the containers to fix the issue.
Any thoughts?
Any associated stack traces or error logs
Error.log
Access.log
Error.log
Access.log
The text was updated successfully, but these errors were encountered: