PM2 stop causes restart of process

[ibrahimab]

Hi,

I am using node v0.10.24, npm version 1.3.21, pm2 version 0.12.3
I just updated pm2 and want to stop a process, but pm2 keeps respawning the process:

pm2 list
Process Name | 0 | fork | 32122 | online | 0 | 15m | 23.334 MB | disabled

pm2 stop 0
Process Name | 0 | fork | 32122 | online | 0 | 0 | 0 B | disabled

pm2 list
Process Name | 0 | fork | 24768 | online | 0 | 3s | 22.562 MB | disabled

[Tjatse]

Did you update PM2 in memory?

$ pm2 updatePM2

[davidcalloway]

I am experiencing this problem as well, node v0.10.35, npm v1.4.28, pm2 v0.12.3. However, it appears to only appear if the script has a server socket running.

pm2 stop [id] appears to restart the process, not stop it.
Similarly, pm2 restart [id] on a running process will stop (and then restart) the process, then start another instance (apparently hidden).
This means that pm2 stop will restart, and pm2 restart will create another instance that constantly dies (in my case) with EADDRINUSE.

For me, I had to pm2 delete [id] and manually kill [pid] the still-running process to get pm2 into a usable state.

[Tjatse]

Hi, @ruquay Maybe it is too later, but could you provide any sample codes to help me reproduce this? (gists will be fine).

[davidcalloway]

@Tjatse I have made a few efforts to reliably reproduce this, but have been unable to do so. I think this occurred for me between upgrading and restarting a server, since then the problem has -- at least for me -- disappeared. Perhaps @ibrahimab can still come up with something?

[ibrahimab]

I have been unable to reproduce this as I deleted all my processes, remove pm2 completely from my system en did a clean install and added the processes again. Since then they cleanly close.

I did update pm2 with the updatePM2 command. I'll try it again when a new update for pm2 is available!

[jshkurti]

This is fixed on the last version of development .
It will be on the next release which is coming very soon.
Thanks for the feedback guys @ibrahimab @ruquay :)