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
Not seeing 'PumaWorkerKiller: Consuming XXX mb' stdout logging after SIGUSR1 signal to master pid #99
Comments
referring to puma ticket as well since I'm not sure if this is just an incompatibility between puma killer and the new fork_worker: puma/puma#2713 |
As a separate issue (I think) but related since it happens every time I start puma or do a phased-restart on macos, I get the following type errors:
|
To make any progress we'll need to reproduce the issue. Can you provide an example app? https://www.codetriage.com/example_app |
I'm closing since |
This is what I have in puma config file
Basically after I do a phased-restart (SIGUSR1), the puma killer stops logging the consumed memory.
The text was updated successfully, but these errors were encountered: