You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: