I am sorry ahead of time if the real question is a replica, but I have done lots of searching and that i haven't found any solutions which help with my problem. I am managing a Rails 3 application with an Ubuntu server with Apache proxying to thin. I'm able to operate a single demonstration of thin or WebBrick, and my application loads on port 3000. I'm while using instructions from Slicehost regarding how to do Apache and Thin for everyone Rails (that we had working previously), but whenever I attempt to begin the daemonized thin processes, the logs for every thin server seem like this:
/[ my application's location]/config/boot.rb:2:in `require': no such file to load -- rubygems (LoadError) from /home/geoff/ldb/doubleday/config/boot.rb:2 from /home/geoff/ldb/doubleday/config/application.rb:1:in `require' from /home/geoff/ldb/doubleday/config/application.rb:1 from /home/geoff/ldb/doubleday/config/environment.rb:2:in `require' from /home/geoff/ldb/doubleday/config/environment.rb:2 from /usr/lib/ruby/1.8/rack/adapter/rails.rb:43:in `require' from /usr/lib/ruby/1.8/rack/adapter/rails.rb:43:in `load_application' from /usr/lib/ruby/1.8/rack/adapter/rails.rb:23:in `initialize' from /usr/lib/ruby/1.8/rack/adapter/loader.rb:36:in `new' from /usr/lib/ruby/1.8/rack/adapter/loader.rb:36:in `for' from /usr/lib/ruby/1.8/thin/controllers/controller.rb:163:in `load_adapter' from /usr/lib/ruby/1.8/thin/controllers/controller.rb:67:in `start' from /usr/lib/ruby/1.8/thin/runner.rb:174:in `send' from /usr/lib/ruby/1.8/thin/runner.rb:174:in `run_command' from /usr/lib/ruby/1.8/thin/runner.rb:140:in `run!' from /usr/bin/thin1.8:6
I am running Ruby 1.9.2, RubyGems 1.5., and RVM. I'm able to start the rails application like a non-daemonized process within the spend as root, myself, or www-data. It appears any time I attempt to operate this like a daemon, it does not load pathways correctly. I have attempted placing atmosphere variables into some files to assist rails find Rubygems, but that does not appear to operate. Any ideas regarding how you can help Rails find Rubygems when it is began with a daemon?
This appears like an RVM error. You can examine how you are loading your thin server, it'll want to use an RVM wrapper or something like that much like configure the best binaries and gemsets.