[Triage] max requests leads to hung workers #3452
Closed
ewdurbin
started this conversation in
Issue Triage
Replies: 3 comments
|
I took a gander at this, and added a diff --git a/tests/test_signal_integration.py b/tests/test_signal_integration.py
index 868e1564..452cc17d 100644
--- a/tests/test_signal_integration.py
+++ b/tests/test_signal_integration.py
@@ -93,6 +93,7 @@ def gunicorn_server(app_module):
'--access-logfile', '-',
'--error-logfile', '-',
'--log-level', 'info',
+ '--max-requests', '1',
app_name
](or two, etc) On a Debian system, test failure: The same on 23.0.0 passes. git bisect points to b650332 - which makes a lot of sense. |
0 replies
|
this is fixed in 3179789 Thanks for the report! New release is landing in a couple of hours. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Type
Bug Report
Description
When setting --max-requests/max_requests and running under Linux, when the worker reaches its auto-restart, it crashes/hangs.
Steps to Reproduce (for bugs)
docker run --rm -it -p 8000:8000 $(docker build -q .)in another terminal:
Observe output from running container
Note that the worker does not recover and is not restarted.
Configuration
Logs / Error Output
No response
Gunicorn Version
gunicorn 24.0.0
Python Version
Python 3.14
Worker Class
sync (default)
Operating System
Debian Trixie
Additional Context
No response
Checklist
All reactions