Peter Hall <[email protected]> wrote:
> Hi,
>
> I'm trying to use unicorn in a test deployment of a Rails app that
> uses Mongoid, so Activerecord isn't included in the app. When I start
> unicorn through Capistrano though, the stderr log fills up endlessly
> with identical ActiveRecord-related errors:
>
> I, [2012-12-05T04:19:25.375952 #5096] INFO -- : Refreshing Gem list
> I, [2012-12-05T04:19:32.941249 #5096] INFO -- : listening on
> addr=/var/www/webapps/fugu-cp/shared/pids/unicorn.sock fd=11
> I, [2012-12-05T04:19:32.990825 #5096] INFO -- : master process ready
> E, [2012-12-05T04:19:33.108183 #5110] ERROR -- : uninitialized
> constant ActiveRecord (NameError)
Hi Peter, this doesn't seem like an issue specific to unicorn...
Can you reproduce this issue using another server, perhaps:
rackup -s webrick -E #{rails_env}
?
<snip>
> This repeats until I kill Unicorn.
>
> If you're curious, the way I'm starting Unicorn in the deploy file is
> as follows:
Which version of Rails is this? Folks more familiar with modern Rails
than myself should be able to help given more information. (Maybe
asking on a Rails-oriented list can help, too).
I do remember it was possible to disable parts of Rails back in the day.
Most of my Rails knowledge is stuck in the Rails 1.x-era, though...
> set :unicorn_rails, "#{deploy_to}/shared/bundle/ruby/1.9.1/bin/unicorn_rails"
> run "cd #{latest_release} && bundle exec \"#{unicorn_rails} -c
> #{deploy_to}/current/config/unicorn.rb -D -E #{rails_env}\""
Probably unrelated to the issue at hand, but "unicorn" is
preferred if you're on Rails >=3.
_______________________________________________
Unicorn mailing list - [email protected]
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
