check gunicorn log's error

Heya @a85f3d362866415d9342a8cebcc419,

The error message “Failed with result ‘service-start-limit-hit’” from journalctl when checking your Gunicorn logs indicates that the Gunicorn service has attempted to start too many times in a short period and has hit the systemd start limit.

What I’ll recommend you is to check your error log apart from what already has been said.

Hey!

This suggests that the Gunicorn service attempted to start multiple times and failed each time, reaching the systemd’s start limit for the service.

Start by checking the detailed status of the Gunicorn service to get more insight into what might be causing the failures:

sudo systemctl status gunicorn.socket

When running sudo journalctl -u gunicorn.socket do you see any other messages right before the Failed with result ‘service-start-limit-hit’ error?

There are a few things that I could suggest checking in addition:

• Check the Nginx error logs by typing: sudo less /var/log/nginx/error.log
• Check the Gunicorn socket logs by typing: sudo journalctl -u gunicorn.socket

If none of those give you any additional information on what the actual problem is, what you can try is to manually start Gunicorn outside of systemd, by running the command inside your Python project’s directory

gunicorn --bind 0.0.0.0:8000 myproject.wsgi:application

This should return the actual error that is causing the restart failures.

Let me know how it goes!

Best,

Bobby