-
Notifications
You must be signed in to change notification settings - Fork 77
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
[ruby] <defunct> #75
Comments
I have 214 defunct processes now. But if the processes still defuncting maybe will be a problem in the future. I'm search and apparently the best way to free the defunct process is killing the parent process. Thanks! |
Can you manually send a SIGTERM to those processes and have them shut down? It seems like the issue is there is something preventing the process from shutting down which would likely be a problem in your app code instead of with puma or puma worker killer. Try running a plain puma process with a “hello world” rack app and see if it still happens. Also make sure puma and PWK are upgraded to the latest. For the processes that are still alive there might be ways to get them to output where they are stuck. Maybe a tool like rbtrace. |
Thanks @schneems I will try rbtrace. Closing this issue for now. |
Hi,
I like that project but I've got a problem with defunct processes.
After the kill action from gem, the killed ruby processes, still are presents in the process list with pid and with defunct state.
Without clean of that processes can be a problem.
Images:
Thanks!
The text was updated successfully, but these errors were encountered: