发生PM2错误=>通过信号[SIGINT]以代码[1]退出

如何解决发生PM2错误=>通过信号[SIGINT]以代码[1]退出

Nodejs在PM2上运行了很长时间。还有一个玉米每天都会清除PM2日志

0 0 * * * find /home/user/.pm2/logs* -mtime +2 -exec rm -rf {} \;

以下错误发生了1000次，然后pm2停止工作，然后当我重新加载该实例时，它仍然可以正常工作。

此错误的原因可能是什么？

/home/user/.nvm/versions/node/v12.16.1/lib/node_modules/pm2/lib/ProcessContainer.js:167
      throw err;
      ^

[Error: ENOENT: no such file or directory,open '/home/user/.pm2/logs/out.log'] {
  errno: -2,code: 'ENOENT',syscall: 'open',path: '/home/user/.pm2/logs/out.log'
}
2020-09-09T00:55:33: PM2 log: App name:app id:1 disconnected
2020-09-09T00:55:33: PM2 log: App exited with code [1] via signal [SIGINT]
2020-09-09T00:55:33: PM2 log: App  starting in -cluster mode-
2020-09-09T00:55:33: PM2 log: App online
/home/user/.nvm/versions/node/v12.16.1/lib/node_modules/pm2/lib/ProcessContainer.js:167
      throw err;
      ^

[Error: ENOENT: no such file or directory,path: '/home/user/.pm2/logs/out.log'
}
2020-09-09T00:55:33: PM2 log: App name:app id:1 disconnected
2020-09-09T00:55:33: PM2 log: App exited with code [1] via signal [SIGINT]
2020-09-09T00:55:33: PM2 log: App starting in -cluster mode-
2020-09-09T00:55:33: PM2 log: App online
/home/user/.nvm/versions/node/v12.16.1/lib/node_modules/pm2/lib/ProcessContainer.js:167
      throw err;
      ^

[Error: ENOENT: no such file or directory,path: '/home/user/.pm2/logs/out.log'
}

解决方法

您正试图仅使用rm来清理日志文件。您不能那样做™。在Linux和其他UNIX派生的操作系统上，即使您从目录rm写入日志文件的程序也将其保持打开状态。直到编写该文件的程序将其关闭（或终止），该文件才真正消失。对于所有类型的软件（不仅是pm2）都是如此。

如果只想清除日志文件并重新开始，则命令pm2 flush适合您。

如果您想在有限的时间内保存旧日志，则应调查pm2's log rotation addon。

像这样的命令可能会帮到您

# install the pm2 addon ... notice it says pm2 install,not npm install
pm2 install pm2-logrotate
# rotate when a logfile fills to ten megabytes
pm2 set pm2-logrotate:max_size 10M
# gzip compress the rotated logs to save space
pm2 set pm2-logrotate:compress true
# force rotation at 00:00 each day even if logfile is not full 
pm2 set pm2-logrotate:rotateInterval '0 0 * * *'

您可以说pm2 config pm2-logrotate来显示它的当前设置。

,

您可以尝试以下两个步骤并检查是否可行。

pm2 start bin/www -i 0 // this will start a cluster and the main app

pm2 stop 0 // this will allow the cluster to keep running