-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
pm2 hangs on kill #316
Comments
Actually when I just broke from it and ran pm2 list still 2 out of the original 4 processes were still running. If it's got open TCP connections it may have issues. If it has open clients... |
I'm having the same issue, not only on kill but for restart and stop as well. If I leave it running for ~10 minutes it will stop / restart eventually. Kind of annoying. I suspect it is caused by open socket.io connections. Edit: took the time and read the docs a bit more carefully, now I see you've already got an option to send a terminate message to the app and gracefully stop all services. Sorry. |
Same problem for me. |
I don't know about this too much anymore. Recently I've been using the command |
Hm I don't think open connections should matter, and I don't know if they matter, like you said @kulicuu you cannot really now if there are open connections. I am on linux and this bug came from nowhere. What I do
kill all pm2 processes and restart them. However this is ugly if you have multiple projects to restart. The owners should def have a look at this problem. @Unitech |
node version @ALL ? |
good point: I'm currently running 11.9 on that one, from 10.26 before. And I might have switched up because of this issue, at least in part. Not sure if it made a difference-- as mentioned my attentions have been elsewhere. |
@soyuka I am on 0.10.26, debian7 |
@artworkad could you try the v0.11.10 ? For a quick update try this |
Memory amount:. Do you mean how much memory is it consuming ? :: (fork mode 4 processes): 124MB, 80MB, 81MB, 81MB. |
Fixed since 0.8.x |
Great program btw. I'm very happy to be using this.
Running on Linode from an npm script.
When I kill it / them (clustered) it just kind of hangs. I can cntrl-C to break and then pm2 list and they're dead processes. So it's not a huge issue.
The text was updated successfully, but these errors were encountered: