Rails - Feb 2010 - 500 error in production environment which I don't get in development env

Hi: I get a strange 500 error in production environment which I don''t
get in development env:
"We''re sorry but something went wrong" message. Production
log is
empty. Write permissions seem to be correct. What gets logged in
production?
that problem get tracked down? Is there a quick possibilty to enable
logging in production env?

-Jens

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.

I solved a part of that problem on my own! By starting Webrick i got
the error details right on the console. What was going wrong?
"undefined method" method occured. A table column could not be found
on a model. Even after running migrations.
The problem was that RAILS_ENV for some unknown reason was set to
development mode. According to that the last migration ran in
development environment. I changed it back with
RAILS_ENV="production", ran migrations and everything was fine again.

Pending question is why my production log is not getting filled on
such errors?! File owner is same as environment.rb and permissions are
ok to write. (I''m running under passenger)

-Jens

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.

Yes Jens, you can enable logging in production:
in your environments/production.rb file enable log level to :debug, as
config.log_level = :debug //uncomment this line

-Gourav

On Feb 11, 12:21 pm, Jens MF
<jens.is.loca...-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
wrote:
> Hi: I get a strange 500 error in production environment which I
don''t
> get in development env:
> "We''re sorry but something went wrong" message.
Production log is
> empty. Write permissions seem to be correct. What gets logged in
> production?
> that problem get tracked down? Is there a quick possibilty to enable
> logging in production env?
>
> -Jens
-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.