14

I deployed a Rails 3.0.3 app to my production server and it's giving me a 500 error. This is being deployed on Dreamhost, so I looked in the logs for my domain and there is nothing and the logs for my app also show nothing.

How do I get Rails displaying actual error messages in production so I can sort this out?

mikewilliamson
  • 24,303
  • 17
  • 59
  • 90

2 Answers2

18

Try changing the consider_all_requests_local setting in environments/production.rb.

Undo
  • 25,519
  • 37
  • 106
  • 129
TK-421
  • 10,598
  • 3
  • 38
  • 34
  • That was my thought as well, but I tried it and restarted my app and it still does not seem to work. Any other thoughts? – mikewilliamson Jan 17 '11 at 03:39
  • Has it ever worked in production (is anything working)? If so, then I would probably evaluate recent changes. If not, and the log files aren't helping, then I would start with a simple test case, a "Hello World" app, and just try to get that running first. – TK-421 Jan 17 '11 at 13:29
  • No its a new app, but really its not much more than a Hello world. It even works if I SSH into the server and run the console in production mode! – mikewilliamson Jan 17 '11 at 16:11
  • 1
    Do you have other Rails apps running successfully on Dreamhost? Not being snarky, just wondering if this is a configuration issue particular to Dreamhost Rails deployments (in which case there may be some blog/newsgroup posts out there covering the gotchas). – TK-421 Jan 18 '11 at 12:47
  • Hey, I do have other apps running on DH, just not Rails 3 ones. This was was such a pain I hosted it on Heroku. It was up and running in seconds. – mikewilliamson Jan 25 '11 at 18:50
2

I had the same issue, it was due to a bug in Aibrake in version 3.1.1. Rollbacking to 3.0.9 solved the issue for me

Chris
  • 2,744
  • 3
  • 24
  • 39