-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 in docker sends SIGKILL to workers when SIGHUP sent to master process #3274
Labels
Comments
antonpetrov145
changed the title
Gunicorn in docker sends SIGKILL to workers in SIGHUP sent to master process
Gunicorn in docker sends SIGKILL to workers when SIGHUP sent to master process
Aug 14, 2024
Does anything besides the SIGTERM error-severity log make you believe that worker shutdown was abnormal? |
@pajod good question, and it seems this is duplicate to the linked issue. Anyway I tried to reload the workers and despite the SIGTERM - workers did consume the requests correctly, but logs get huge with messages like these
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello all, I have flask-gunicorn api running in docker but the issue is this:
when sending SIGHUP to the master process, in docker it is 1, workers get SIGKILL signals - not gracefully stopped.
this is my config in docker
gunicorn version - 23.0.0
logs show
gunicorn version - 20.0.4 all works as expected
what am I doing wrong?
The text was updated successfully, but these errors were encountered: