Displaying 4 results from an estimated 4 matches for "buffered_logger".
2009 May 19
1
logging with the daemons gem
...confused about the
proper way to set up logging. I am able pass options which configure
stdout to go to a log file but it seems like all calls to Rails.logger
are disabled as I see the following message in my output:
usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/
active_support/buffered_logger.rb:99:in `write'': closed stream (IOError)
from /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/
lib/active_support/buffered_logger.rb:99:in `flush''
from /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/
lib/active_support/buffered_logger.rb:96:in `sy...
2008 Feb 28
2
random exception driving me crazy: SecurityError (Insecure: can't modify array)
...ve.
The exception is occurring from a seemingly innocuous line in my code,
a simple ''logger.warn("some debug information")''. The backtrace
follows:
SecurityError (Insecure: can''t modify array)
[RAILS_ROOT]/vendor/rails/activesupport/lib/active_support/buffered_logger.rb:68:in
`<<''
[RAILS_ROOT]/vendor/rails/activesupport/lib/active_support/buffered_logger.rb:68:in
`add''
[RAILS_ROOT]/vendor/rails/activesupport/lib/active_support/buffered_logger.rb:75:in
`warn''
[RAILS_ROOT]/app/models/order.rb:244:in `proces...
2009 Jun 04
0
Error with Rails.logger: closed stream (IOError)
Hi all.
I am creating a plugin that uses the daemons gem to run some code in the
background. In that code, I call Rails.logger.info "message", but
receive the following error.
/opt/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/active_support/buffered_logger.rb:99:in
`write'': closed stream (IOError)
Anyone seen this before and have any idea what''s going on?
Thanks,
Chris
--
Posted via http://www.ruby-forum.com/.
2012 Oct 05
1
Is Rails Logger Thread Safe?
Is Rails Logger truly not Thread Safe?
http://log.kares.org/2011/04/railslogger-is-not-threadsafe.html
This seems like an issue that should have been picked up quite a long time
ago. I just set config.threadsafe! in my config/application.rb and my log
output from rails server has completely disappeared.
If the logger is not thread-safe, I cannot help but wonder how much of the
Rails core is