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
gunicorn stops working every few months (light load) #2876
Comments
what does your flask application? can you kill a worker manually and the worker is restarted? |
My Flask application serves web pages... very common usage; nothing "exotic". I will try to kill a worker manually - and see if it restarts, thanks. 2 weeks ago, I dropped the part |
@BrainAnnex well hard to say since i don't reproduce it myself. Did you try to kill manually a worker with same configuration? Do you have none ssl connection landing on gunicorn from time to time? In any case coming update has new SSL handling. |
I dropped the part
Now, while not crashing, it produces mountains of errors in the log file; they all say:
After the last of many, it also said:
It presumably re-starts: I'm getting logged out of my Flask web app about once/day... sometimes mid-use, and sometimes at times of no apparent use (I'm the only person on that web app) As usual, I'm seeing two processes:
Maybe the short running time on the 2nd process is related to the fact that it restarted minutes ago? (And logged me out as a result?) Following your advice, I manually killed a process:
and it re-started (logging me out of the Flask web app by doing so) Now the end of the gunicorn error log says:
So, it seems that we have:
|
same issue starting with gunicorn app:app and works fine for a day then after 1 day one of the actions stops responding while everything else is working fine. |
I have an HTTPS site with very light load - I'm the only one using it.
Hosted on Debian server on Google cloud.
Runs fine for months - then the next day it's completely unresponsive. Happened SEVERAL times. Re-starting gunicorn always fixes the issue... but it's clearly an unreliable situation!
No Ngix, nor load balancers, nor anything else: JUST gunicorn (version 20.1.0) + Flask site (with an SSL certificate.)
Here's how I start gunicorn:
There's nothing unusual in the app log. In the
gunicorn_error_log.txt
, the last message before becoming unresponsive was:However, this is a message that is sprinkled throughout the error log site! So, maybe not serious - until it dies! (Or maybe it dies silently from something else?)
Strangely, even though the app is 100% un-responsive, if I do:
ps -e | grep gunicorn
it shows 2 processes, as it normally does.
So, it seems that gunicorn has NOT exited; it has simply become un-responsive...
As stated at the beginning, re-starting gunicorn fixes the issue, but then a few months later - again! This has happened at the very least 3-4 times :(
The text was updated successfully, but these errors were encountered: