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

Restarting PM2 after hard kill/crash doesn't rediscover running processes #723

Closed
rsheldon opened this issue Sep 20, 2014 · 2 comments
Closed

Comments

@rsheldon
Copy link

If PM2 is running with a number of processes, and crashes or is harshly killed then the processes it manages are left around. That's fine. The problem is that when pm2 restarts it doesn't auto-detect these processes. This normally means we have to stop the processes by hand, and then restart with PM2 in order to get them managed again.

I know that the list of pids for the old processes are there in the ~/.pm2/pids diretory, so is there any way for pm2 to check/reconnect to these processes?

@solarfly73
Copy link

I've experienced the same issue recently on crashes when stopping a process. For some reason, when pm2 crashes, the dump file that was created by 'pm2 dump' is truncated or missing. I have to re-run pm2 start /foo/processes.json (our pm2 process config file) to bring everything back and then dump it again.

@Unitech
Copy link
Owner

Unitech commented Oct 11, 2014

Process are flushed on PM2 exceptions since the 0.11

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

3 participants