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.
irb(main):001:0> Rails.logger
=> #<ActiveSupport::BufferedLogger:0xb6729640 @guard=#<Mutex:
0xb6715fa0>, @buffer={}, @auto_flushing=1000, @level=1, @log=#<File:/u/
apps/billbaba/releases/20110423222330/log/production.log>>
Any thoughts......anything I might have messed up....???
Regards,
Amit
On Apr 24, 3:51 am, amit_saxena <[email protected]> wrote:
> Hi,
>
> I was debugging the problem of nothing being written in my production
> logs (it works fine in development mode), although the application was
> working fine. On investigating I found out that
> Rails.logger.auto_flushing was being set to 1000 in production mode.
>
> I upgraded from rails 3.0.3 to 3.0.7 thinking that it might be an
> issue with that version, but the problem still persists. I have fixed
> the problem temporarily by adding Rails.logger.auto_flushing =1 in my
> environment file, but am not able to establish as to why is this
> happening. Why is auto_flushing being set to 1000 in production mode?
>
> Regards,
> Amit
--
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.
