On 24 April 2011 13:04, amit_saxena <[email protected]> wrote: > Rails.logger.auto_flushing = 1 in production environment file is also > throwing an exception. > > It seems that the logger is not being initialized, as Rails.logger is > being returned as nil, but on console it returns an > ActiveSupport::BufferedLogger object.
What happens if you make a new app and run in production mode? If that is ok then you could go back to earlier versions of your app from your version control system and see at what point the log stopped working. Alternatively, I believe the only differences between development and production are in environments/development.rb and production.rb (plus database.yml). Compare the two rb files and if nothing is obvious change production.rb so that it becomes more like development.rb until the logger starts working. Colin -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
