James Cox <[email protected]> wrote: > trying to start my unicorn via bluepill, and running into this : > > Starting unicorn...\n{:unicorn_options=> > {:config_file=>"/home/configs/unicorn/marketing.rb", :listeners=>[]}, > :daemonize=>true, > :app=> > > #<Proc:0x000000001042c718@/usr/local/rvm/gems/ree-1.8.7-2010.01/gems/unicorn-0.97.0/bin/unicorn_rails:120>} > Exception `Errno::EEXIST' at > /usr/local/rvm/rubies/ree-1.8.7-2010.01/lib/ruby/1.8/fileutils.rb:243 > - File exists - tmp/cache > Exception `Errno::EEXIST' at > /usr/local/rvm/rubies/ree-1.8.7-2010.01/lib/ruby/1.8/fileutils.rb:243 > - File exists - tmp/pids > Exception `Errno::EEXIST' at > /usr/local/rvm/rubies/ree-1.8.7-2010.01/lib/ruby/1.8/fileutils.rb:243 > - File exists - tmp/sessions > Exception `Errno::EEXIST' at > /usr/local/rvm/rubies/ree-1.8.7-2010.01/lib/ruby/1.8/fileutils.rb:243 > - File exists - tmp/sockets > Exception `EOFError' at > /usr/local/rvm/gems/ree-1.8.7-2010.01/gems/unicorn-0.97.0/lib/unicorn/launcher.rb:45 > - end of file reached > master failed to start, check stderr log for details > > > it's a rather complicated setup etc, but essentially i've got bluepill > instructing a start script which sets the right version of ruby just > before hand (i.e. the rvm stuff). > > I can run it manually by going into the RAILS_ROOT and running it, but > trying to run via bluepill explodes. > > any ideas?
I'm not familiar with Bluepill, it's a process monitor of some sort. Both you and Greg are using unicorn_rails which did get some overhauling in Unicorn 0.97.0. Everything seems fine on my end, but maybe there's a piece of the puzzle I'm overlooking.. I'll dig further. -- Eric Wong _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
