我正在使用pm2来管理 Node 进程。
当前，即使pm2干净完成(退出代码为0)，pm2也会重新启动 Node 进程。我不希望那样发生。
相反，我只希望当 Node 进程以代码!= 0退出时，PM2重新启动应用程序。
这该怎么做？
pm2日志可能有用:
PM2 | App [xxx] with id [0] and pid [44797], exited with code [0] via signal [SIGINT]
PM2 | Starting execution sequence in -fork mode- for app name:xxx id:0
PM2 | App name:xxx id:0 online
编辑:
似乎在群集模式下启动过程按我的预期工作。即:重新启动仅发生在退出代码!= 0上。
仍然以fork模式启动会产生上述意外情况。
最佳答案
我看过pm2的代码
https://github.com/Unitech/pm2/blob/6090b0971abca6fcb2d796e560f2a72b81ab5707/lib/God.js
在成功退出时不启动流程方面似乎没有任何逻辑。您要的功能不存在。对于集群以及 fork 模式都相同。
您可以使用test.js进行测试
setTimeout(()=>process.exit(), 2000);
fork 模式
$ pm2 start test.js && sleep 5
[PM2] Starting /Users/tarunlalwani/Documents/Projects/SO/pm2exit/test.js in fork_mode (1 instance)
[PM2] Done.
┌──────────┬────┬─────────┬──────┬──────┬────────┬─────────┬────────┬─────┬──────────┬──────────────┬──────────┐
│ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │
├──────────┼────┼─────────┼──────┼──────┼────────┼─────────┼────────┼─────┼──────────┼──────────────┼──────────┤
│ test │ 0 │ N/A │ fork │ 5889 │ online │ 0 │ 0s │ 0% │ 9.4 MB │ tarunlalwani │ disabled │
└──────────┴────┴─────────┴──────┴──────┴────────┴─────────┴────────┴─────┴──────────┴──────────────┴──────────┘
Use `pm2 show <id|name>` to get more details about an app
$ pm2 logs
PM2 | 2019-08-18T11:40:23: PM2 log: App [test:0] exited with code [0] via signal [SIGINT]
PM2 | 2019-08-18T11:40:23: PM2 log: App [test:0] starting in -fork mode-
PM2 | 2019-08-18T11:40:23: PM2 log: App [test:0] online
PM2 | 2019-08-18T11:40:25: PM2 log: App [test:0] exited with code [0] via signal [SIGINT]
PM2 | 2019-08-18T11:40:25: PM2 log: App [test:0] starting in -fork mode-
PM2 | 2019-08-18T11:40:25: PM2 log: App [test:0] online
$ pm2 delete test
$ pm2 start test.js -i 2&& sleep 5
[PM2] Starting /Users/tarunlalwani/Documents/Projects/SO/pm2exit/test.js in cluster_mode (2 instances)
[PM2] Done.
┌──────────┬────┬─────────┬─────────┬──────┬────────┬─────────┬────────┬─────┬───────────┬──────────────┬──────────┐
│ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │
├──────────┼────┼─────────┼─────────┼──────┼────────┼─────────┼────────┼─────┼───────────┼──────────────┼──────────┤
│ test │ 0 │ N/A │ cluster │ 5993 │ online │ 0 │ 0s │ 0% │ 27.6 MB │ tarunlalwani │ disabled │
│ test │ 1 │ N/A │ cluster │ 5994 │ online │ 0 │ 0s │ 0% │ 20.8 MB │ tarunlalwani │ disabled │
└──────────┴────┴─────────┴─────────┴──────┴────────┴─────────┴────────┴─────┴───────────┴──────────────┴──────────┘
Use `pm2 show <id|name>` to get more details about an app
$ pm2 logs
PM2 | App name:test id:0 disconnected
PM2 | App [test:0] exited with code [0] via signal [SIGINT]
PM2 | App [test:0] starting in -cluster mode-
PM2 | App name:test id:1 disconnected
PM2 | App [test:1] exited with code [0] via signal [SIGINT]
PM2 | App [test:1] starting in -cluster mode-
PM2 | App [test:0] online
PM2 | App [test:1] online
PM2 | App name:test id:0 disconnected
PM2 | App [test:0] exited with code [0] via signal [SIGINT]
PM2 | App [test:0] starting in -cluster mode-
PM2 | App name:test id:1 disconnected
PM2 | App [test:1] exited with code [0] via signal [SIGINT]
PM2 | App [test:1] starting in -cluster mode-
PM2 | App [test:0] online
PM2 | App [test:1] online
PM2 | App name:test id:0 disconnected
$ pm2 delete test
替代
或者，您可以使用Supervisord
您可以在配置文件中使用
exitcodeshttp://supervisord.org/configuration.html
关于node.js - 如果退出代码!= 0，如何仅使用PM2重新启动 Node 进程，我们在Stack Overflow上找到一个类似的问题：https://stackoverflow.com/questions/43614017/