views:

366

answers:

2

I'm writing a project at the moment in Ruby which makes use of the ActiveRecord gem for database interaction and I'm trying to log all the database activity using the ActiveRecord::Base.logger attribute with the following code

ActiveRecord::Base.logger = Logger.new(File.open('logs/database.log', 'a'))

This works fine for migrations etc (which for some reason seem to require that logging be enabled as it gives a NilClass error when it's disabled) but when I try to run the project which includes a threaded daemon calling the ActiveRecord object the script fails with the following error

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/logger.rb:504:in `write': closed stream (IOError)

Any ideas on how to solve this problem would be greatly appreciated. For the moment I've started to look through other code to see if people have other ways of implementing ActiveRecord logging in a more thread-safe manner

Thanks

Patrick

+1  A: 

It turns out that for migrations to work the ActiveRecord::Base.logger variable cannot be nil, which explains the first half of the problem. I am as yet unable to fix the IOError though when a file is used instead of STDERR.

Patrick O'Doherty
Would the problem stem from synchronization? Could you use Rails' BufferedLogger instead, and see if that fixed the problem?
François Beausoleil
We ended up writing a simple logging application for our needs using DRB which handled errors for all our threads
Patrick O'Doherty
+1  A: 

I ran into the same issue. You need to daemonize first, and then load the Rails environment.

Logan Koester
Could you explain what you mean by "daemonize and then load Rails env"
Chris Kimpton
Daemons.run_proc('your_daemon', daemon_options) { require File.expand_path(File.join(File.dirname(__FILE__), '..', 'config', 'environment')) # do stuff }
Logan Koester