Skip to content
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

Process still listening despite "pm2 stop". #369

Closed
ghost opened this issue Mar 31, 2014 · 2 comments
Closed

Process still listening despite "pm2 stop". #369

ghost opened this issue Mar 31, 2014 · 2 comments

Comments

@ghost
Copy link

ghost commented Mar 31, 2014

Observed on a standard CentOS AWS instance (Node.js 10.26 stable):

  1. Stop a script using "pm2 stop ".
  2. Try to run same script using node script.js
  3. Get "Address in use error"
  4. Check open end-points via "netstat -tulpn"
  5. Process "pm2" is still listening on the stopped script's end-point !

I think when pm2 stops a script, the address and port it was using should be freed up as well. Can this be fixed ?

@rlidwka
Copy link
Collaborator

rlidwka commented Mar 31, 2014

I guess an update to node 0.11.x would fix it.

@Unitech
Copy link
Owner

Unitech commented Apr 4, 2014

Yes, can't wait for that stable node v0.12.x !! (:

#74

@Unitech Unitech closed this as completed Apr 4, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants