CODEWITHSUNDEEP
ruby-on-railslogging
Sprachprofi
Sprachprofi

Reputation: 1259

Error page but Rails log says everything's fine

One of my clients is getting the standard "Something went wrong" error page on the production server, however the production.log claims that the page was rendered correctly.

Started GET "/translations" for **IP** at 2012-06-07 08:30:56 +0000
Processing by TranslationsController#index as HTML
  Rendered translations/_filters.html.erb (1.9ms)
  Rendered glossary_terms/_form.html.erb (3.4ms)
  Rendered translations/index.html.erb within layouts/application (125.8ms)
Completed 200 OK in 131ms (Views: 119.4ms | ActiveRecord: 8.6ms)

I have verified that this is indeed her request being logged, and that she shift-reloaded the page. Also, I cannot reproduce the error locally; the page loads fine for me and several other people.

Upvotes: 0

Views: 99

Answers (1)

edralph
edralph

Reputation: 1831

It's one of those bugs where you have to go and enumerate all those things that are different between your environment and the clients. Check things like:

  • Cookies
  • Session state
  • Browser version (the response might be a 200, but it might be malformed)
  • Use Sam Spade to view the raw response - might be a clue in there
  • Double check that it is her request being logged
  • Can she reproduce it without fail?
  • Has she tried with different browsers? Different machine?
  • Maybe the 'something went wrong' error is being served as a 200 response?

Upvotes: 1

Related Questions