在日志中没有错误消息时，如何诊断Heroku上的500错误？ [英] How do you diagnose a 500 error on Heroku when there is no error message in the logs?

问题描述

Heroku上有一个Rails应用程序，它随机发送500个错误。网页将以纯文本形式显示内部服务器错误，而不是通常的我们很抱歉，出错了。页。当我刷新页面时，它工作正常。

日志不会显示错误消息，只是

 »14：20：34.107 2013-10-11 12：20：33.763690 + 00：00 heroku路由器 -   -  at = info method = HEAD path = / host = www.mydomain。 dyno = web.1 connect = 1ms service = 63ms status = 200 bytes = 0 
»14： 21：03.957 2013-10-11 12：21：03.561867 + 00：00 heroku路由器 -   -  at = info method = GET path = / host = www.mydomain.com fwd =50.112.95.211/ec2-50-112- 95-211.us-west-2.compute.amazonaws.comdyno = web.1 connect = 0ms service = 1ms status = 500 bytes = 21 
  

支持让我看看New Relic中的请求排队，但New Relic只显示一个大的红色标记，表示服务器关闭（即使网站在刷新时工作正常）。

没有错误信息，我不知道如何诊断这个问题。

解决方案

在Heroku中，我用 LogEntries - 它比Heroku日志更容易诊断错误。

我所做的是加载应用程序，然后在LogEntries面板中转到Live（Beta）。这显示出现的任何错误，并且通常非常具有解释性。

只是可能有所帮助的一些东西

I have a Rails app on Heroku that is serving 500 errors at random intervals. Web pages will display "Internal server error" in plain text, instead of the usual "We're sorry. Something went wrong." page. When I refresh the page, it works fine.

The logs don't show me an error message, just

» 14:20:34.107 2013-10-11 12:20:33.763690+00:00 heroku router - - at=info method=HEAD path=/ host=www.mydomain.com fwd="184.73.237.85/ec2-184-73-237-85.compute-1.amazonaws.com" dyno=web.1 connect=1ms service=63ms status=200 bytes=0
» 14:21:03.957 2013-10-11 12:21:03.561867+00:00 heroku router - - at=info method=GET path=/ host=www.mydomain.com fwd="50.112.95.211/ec2-50-112-95-211.us-west-2.compute.amazonaws.com" dyno=web.1 connect=0ms service=1ms status=500 bytes=21

Support has told me to look at request queuing in New Relic, but New Relic only shows a big red mark saying the server is down (even though the site works fine when refreshed).

With no error messages, I'm at a loss for how to diagnose this issue.

解决方案

In Heroku, I diagnose errors with LogEntries -- its far easier than the Heroku logs to diagnose errors.

What I do is load up the app, and in the LogEntries panel, go to "Live (Beta)". This shows any errors which appear, and are generally very explanatory

Just something that might help

这篇关于在日志中没有错误消息时，如何诊断Heroku上的500错误？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！