How do you diagnose a 500 error on Heroku when there is no error message in the logs?

Posted by lala on Stack Overflow See other posts from Stack Overflow or by lala
Published on 2013-10-16T18:18:18Z Indexed on 2013/10/19 9:55 UTC
Read the original article Hit count: 289

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.

© Stack Overflow or respective owner

Related posts about ruby-on-rails

Related posts about heroku