Open pierreclr opened 8 years ago
same issue here, I think it started after updated pm2 to 1.1.2. my process is running fine until I push the new code for deploy. pm2-auto-pull then kills my process (pm2 list shows it as stopped and if I try pm2 start myprocess, it never starts.) The only option is pm2 kill and then start all processes again. I didn't find any info in logs.
----------see attached output from pm2 list. As you can see pm2-auto-pull jumps from modules to apps section and kills st-main process after it detects new commit. (Before it was correctly in Modules section)
â App name â id â mode â pid â status â restart â uptime â memory â watching â
â pm2-auto-pull â 2 â fork â 6001 â online â 1 â 20s â 38.414 MB â disabled â â st-main â 3 â fork â 0 â stopped â 2 â 0 â 0 B â disabled â â st-blog â 4 â fork â 4758 â online â 0 â 4m â 84.672 MB â disabled â
Module activated
â Module â version â target PID â status â restart â cpu â memory â
â pm2-server-monit â 1.1.0 â 4730 â online â 0 â 0% â 20.508 MB â â pm2-mongodb â 0.4.3 â 4739 â online â 0 â 0% â 24.648 MB â
I have the same problem... this ticket seems to have been open for a long time. Any progress on the issue?
@vmarchaud, would you mind to have a quick check of this issue? Code is straightforward: https://github.com/pm2-hive/pm2-auto-pull/blob/master/app.js
Thanks
Seems like this issue https://github.com/Unitech/pm2/issues/2270 cause the bug.
Hi, I have a serious problem actually. When I push some new code to my repo pm2-auto-pull works but once the new code is pull it deletes all my processes. Do you know how can I solve this problem ?
Thank you