blocks|key|683755|text|我把这段代码放在我的require语句和全局声明下面：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|683756|process.on('uncaughtException',+function+(err)+{
++console.error(err);
++console.log("Node+NOT+Exiting...");
});|code-block|syntax|javascript|683757|这对我很有效。我唯一不喜欢的是，如果我只是让它崩溃，我得到的信息就不会那么多了。|683758|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I put this code right under my require statements and global declarations:

<pre><code>process.on('uncaughtException', function (err) {
 console.error(err);
 console.log("Node NOT Exiting...");
});
</code></pre>

works for me. the only thing i don't like about it is I don't get as much info as I would if I just let the thing crash.

blocks|key|900313|text|正如前面提到的here，您会发现error.stack提供了更完整的错误消息，比如导致错误的行号：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|900314|process.on('uncaughtException',+function+(error)+{
+++console.log(error.stack);
});|code-block|syntax|javascript|900315|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/9181027/node-js-doesnt-display-entire-error-message-on-uncaughtexception-is-it-possibl^0|G|B|7|4|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

As mentioned <a href="https://stackoverflow.com/questions/9181027/node-js-doesnt-display-entire-error-message-on-uncaughtexception-is-it-possibl">here</a> you'll find <code>error.stack</code> provides a more complete error message such as the line number that caused the error:

<pre><code>process.on('uncaughtException', function (error) {
 console.log(error.stack);
});
</code></pre>

blocks|key|683674|text|试试supervisor|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|683675|npm+install+supervisor
supervisor+app.js|code-block|syntax|javascript|683676|或者，您也可以安装forever。|683677|所要做的就是在服务器崩溃时通过重新启动来恢复它。|683678|可以在代码中使用forever来正常恢复任何崩溃的进程。|683679|forever文档提供了关于以编程方式退出/错误处理的可靠信息。|683680|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/isaacs/node-supervisor|1|https://github.com/foreverjs/forever^0|2|A|2|A|0|0|0|9|7|9|7|1|0|0|8|7|0|0|7|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@$9|15|A|16|1|17]]|E|$]]|$1|F|3|G|5|H|7|18|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|M|3|N|5|6|7|1F|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1G|8|@$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1J|8|@$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]|10|$5|V|W|X|E|$Y|11]]]]

Try <a href="https://github.com/isaacs/node-supervisor" rel="nofollow"><code>supervisor</code></a>

<pre><code>npm install supervisor
supervisor app.js
</code></pre>

Or you can install <a href="https://github.com/foreverjs/forever" rel="nofollow"><code>forever</code></a> instead.

All this will do is recover your server when it crashes by restarting it.

<code>forever</code> can be used within the code to gracefully recover any processes that crash.

The <code>forever</code> docs have solid information on exit/error handling programmatically.

blocks|key|683843|text|尝试一下pm2节点模块，它非常一致，并且有很好的文档。具有内置负载均衡器的Node.js应用程序的生产流程管理器。请避免使用uncaughtException解决此问题。https://github.com/Unitech/pm2|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|683844|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/Unitech/pm2^0|2D|U|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Give a try to pm2 node module it is far consistent and has great documentation. Production process manager for Node.js apps with a built-in load balancer. please avoid uncaughtException for this problem. 
<a href="https://github.com/Unitech/pm2" rel="nofollow">https://github.com/Unitech/pm2</a>

blocks|key|683929|text|在restify上效果很好：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|683930|server.on('uncaughtException',+function+(req,+res,+route,+err)+{
++log.info('*******+Begin+Error+*******\n%25s\n*******\n%25s\n*******+End+Error+*******',+route,+err.stack);
++if+(!res.headersSent)+{
++++return+res.send(500,+{ok:+false});
++}
++res.write('\n');
++res.end();
});|code-block|syntax|javascript|683931|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Works great on restify:

<pre><code>server.on('uncaughtException', function (req, res, route, err) {
 log.info('******* Begin Error *******\n%s\n*******\n%s\n******* End Error *******', route, err.stack);
 if (!res.headersSent) {
 return res.send(500, {ok: false});
 }
 res.write('\n');
 res.end();
});
</code></pre>

blocks|key|683894|text|UncaughtException是“一种非常粗糙的机制”(这是真的)，域名现在已经被弃用了。然而，我们仍然需要一些机制来捕获(逻辑)域周围的错误。库：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|683895|https://github.com/vacuumlabs/yacol|offset|length|683896|可以帮助你做到这一点。只需一点额外的编写，你就可以在你的代码周围拥有很好的领域语义！|683897|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|Z|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

UncaughtException is "a very crude mechanism" (so true) and domains are deprecated now. However, we still need some mechanism to catch errors around (logical) domains. The library:

<a href="https://github.com/vacuumlabs/yacol" rel="nofollow noreferrer">https://github.com/vacuumlabs/yacol</a>

can help you do this. With a little of extra writing you can have nice domain semantics all around your code!

blocks|key|683974|text|默认情况下，Node.js通过将堆栈跟踪打印到stderr并使用代码1退出，覆盖任何以前设置的process.exitCode来处理此类异常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|683975|know+more|offset|length|683976|process.on('uncaughtException',+(err,+origin)+=>+{
++++console.log(err);
});|code-block|syntax|javascript|683977|entityMap|0|LINK|mutability|MUTABLE|url|https://nodejs.org/dist/latest-v16.x/docs/api/process.html#process_event_uncaughtexception^0|0|0|9|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@$D|U|E|V|1|W]]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

By default, Node.js handles such exceptions by printing the stack trace to stderr and exiting with code 1, overriding any previously set process.exitCode.
<a href="https://nodejs.org/dist/latest-v16.x/docs/api/process.html#process_event_uncaughtexception" rel="nofollow noreferrer">know more</a>
<pre><code>process.on('uncaughtException', (err, origin) =&gt; {
 console.log(err);
});
</code></pre>

From my experience, a php server would throw an exception to the log or to the server end, but node.js just simply crashes. Surrounding my code with a try-catch doesn't work either since everything is done asynchronously. I would like to know what does everyone else do in their production servers.

How do I prevent node.js from crashing? try-catch doesn't work

负载均衡

服务器

根据我的经验，php服务器会向日志或服务器端抛出异常，但node.js只是简单地崩溃。使用try-catch包围我的代码也不起作用，因为一切都是异步完成的。我想知道其他人在他们的生产服务器上做什么。

问如何防止node.js崩溃？try-catch不起作用
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何防止node.js崩溃？try-catch不起作用EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何防止node.js崩溃？try-catch不起作用
EN