[英]How to find which error has caused pm2 to restart
I'm running a Node.js puppeteer script with pm2 .我正在使用pm2运行 Node.js puppeteer脚本。 It's important to keep this process stable.保持这个过程稳定很重要。 After 2 days of work I see 2 restarts in my pm2 stats.工作 2 天后,我在 pm2 统计信息中看到 2 次重启。
I want to find out what is causing the restarts.我想找出导致重新启动的原因。 In my error logs I see 3 main errors:在我的错误日志中,我看到 3 个主要错误:
Error: Page crashed (puppeteer )
Error: Quit inactivity timeout (mysql)
or: Timed out after 30000 ms while trying to connect to Chrome! (puppeteer )
Here is my error log (I've only left the first error's full stack data, since the similar errors have the same stack)这是我的错误日志(我只留下了第一个错误的完整堆栈数据,因为类似的错误具有相同的堆栈)
Error: Page crashed!
at Page._onTargetCrashed (/home/mysite/domains/mysite.xyz/laravel/robots/node_modules/puppeteer/lib/Page.js:156:24)
at CDPSession.Page.client.on.event (/home/mysite/domains/mysite.xyz/laravel/robots/node_modules/puppeteer/lib/Page.js:132:56)
at CDPSession.emit (events.js:198:13)
at CDPSession._onMessage (/home/mysite/domains/mysite.xyz/laravel/robots/node_modules/puppeteer/lib/Connection.js:232:12)
at Connection._onMessage (/home/mysite/domains/mysite.xyz/laravel/robots/node_modules/puppeteer/lib/Connection.js:119:19)
at WebSocket.emit (events.js:198:13)
at Receiver.receiverOnMessage (/home/mysite/domains/mysite.xyz/laravel/robots/node_modules/ws/lib/websocket.js:720:20)
at Receiver.emit (events.js:198:13)
at Receiver.dataMessage (/home/mysite/domains/mysite.xyz/laravel/robots/node_modules/ws/lib/receiver.js:414:14)
at Receiver.getData (/home/mysite/domains/mysite.xyz/laravel/robots/node_modules/ws/lib/receiver.js:346:17)
Error: Page crashed!
Error: Page crashed!
Error: Page crashed!
Error: Page crashed!
{ Error: Quit inactivity timeout
at Quit.<anonymous> (/home/mysite/domains/mysite.xyz/laravel/robots/node_modules/mysql/lib/protocol/Protocol.js:163:17)
at Quit.emit (events.js:198:13)
at Quit._onTimeout (/home/mysite/domains/mysite.xyz/laravel/robots/node_modules/mysql/lib/protocol/sequences/Sequence.js:124:8)
at Timer._onTimeout (/home/mysite/domains/mysite.xyz/laravel/robots/node_modules/mysql/lib/protocol/Timer.js:32:23)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
code: 'PROTOCOL_SEQUENCE_TIMEOUT',
fatal: true,
timeout: 30000 }
{ Error: Quit inactivity timeout}
Error: Timed out after 30000 ms while trying to connect to Chrome! The only Chrome revision guaranteed to work is r564778
at Timeout.onTimeout (/home/mysite/domains/mysite.xyz/laravel/robots/node_modules/puppeteer/lib/Launcher.js:296:14)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
Error: Timed out after 30000 ms while trying to connect to Chrome! The only Chrome revision guaranteed to work is r564778
Error: Timed out after 30000 ms while trying to connect to Chrome! The only Chrome revision guaranteed to work is r564778
How can I find out which error has caused the restart?如何找出导致重新启动的错误?
ps: Guys I've already posted the logs in my question, I know how to check the logs! ps:伙计们,我已经在我的问题中发布了日志,我知道如何检查日志! Please read the question carefully!请仔细阅读问题!
To check the logs of why the process has restarted you can try multiple ways:要检查进程重启原因的日志,您可以尝试多种方法:
pm2 logs fileName.js
Register exceptionHandlers for Node.js process for catching different exceptions.为 Node.js 进程注册 exceptionHandlers 以捕获不同的异常。
Reference: https://nodejs.org/api/process.html#process_warning_using_uncaughtexception_correctly参考: https://nodejs.org/api/process.html#process_warning_using_uncaughtexception_correctly
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.