我在 ubuntu 机器上的生产环境中运行我的 rails 应用程序时遇到问题。我已将其配置为在 nginx 前面的独角兽上运行。rails 应用程序使用我自己编写的 gem，它位于 rails 应用程序文件夹的旁边。所以在我的 gemfile 我有 gem 'my_gem', path: '../app'
如果我尝试使用以下命令启动 rails 应用程序：
bundle exec unicorn_rails -c /var/www/portlogs/web/config/unicorn.rb -D
我收到以下错误：
/root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/activesupport-3.1.0/lib/active_support
/dependencies.rb:240:in `require': no such file to load -- ship_app/readmodels/Search
(LoadError)
from /root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/activesupport-3.1.0/lib
/active_support/dependencies.rb:240:in `block in require'
from /root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/activesupport-3.1.0/lib
/active_support/dependencies.rb:223:in `block in load_dependency'
from /root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/activesupport-3.1.0/lib
/active_support/dependencies.rb:640:in `new_constants_in'
from /root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/activesupport-3.1.0/lib
/active_support/dependencies.rb:223:in `load_dependency'
from /root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/activesupport-3.1.0/lib
/active_support/dependencies.rb:240:in `require'
from /var/www/portlogs/app/lib/ship_app.rb:43:in `<top (required)>'
from /root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/bundler-1.2.3/lib/bundler
/runtime.rb:68:in `require'
from /root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/bundler-1.2.3/lib/bundler
/runtime.rb:68:in `block (2 levels) in require'
from /root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/bundler-1.2.3/lib/bundler
/runtime.rb:66:in `each'
from /root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/bundler-1.2.3/lib/bundler
/runtime.rb:66:in `block in require'
from /root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/bundler-1.2.3/lib/bundler
/runtime.rb:55:in `each'
from /root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/bundler-1.2.3/lib/bundler
/runtime.rb:55:in `require'
from /root/.rvm/gems/ruby-1.9.2-p290@portlogs/gems/bundler-1.2.3/lib
/bundler.rb:128:in `require'
from /var/www/portlogs/web/config/application.rb:12:in `<top (required)>'
from /var/www/portlogs/web/config/environment.rb:2:in `require'
from /var/www/portlogs/web/config/environment.rb:2:in `<top (required)>'
from config.ru:4:in `require'
from config.ru:4:in `block in <main>'
ship_app/readmodels/Search 文件位于 my_gem 中。但我不明白为什么独角兽无法加载它。如果我在本地机器上使用 rails 运行它，一切正常。
这是我的独角兽配置：
APP_PATH = "/var/www/portlogs/web"
# Sample verbose configuration file for Unicorn (not Rack)
#
# This configuration file documents many features of Unicorn
# that may not be needed for some applications. See
# http://unicorn.bogomips.org/examples/unicorn.conf.minimal.rb
# for a much simpler configuration file.
#
# See http://unicorn.bogomips.org/Unicorn/Configurator.html for complete
# documentation.
# Use at least one worker per core if you're on a dedicated server,
# more will usually help for _short_ waits on databases/caches.
worker_processes 4
# Since Unicorn is never exposed to outside clients, it does not need to
# run on the standard HTTP port (80), there is no reason to start Unicorn
# as root unless it's from system init scripts.
# If running the master process as root and the workers as an unprivileged
# user, do this to switch euid/egid in the workers (also chowns logs):
# user "unprivileged_user", "unprivileged_group"
# Help ensure your application will always spawn in the symlinked
# "current" directory that Capistrano sets up.
working_directory APP_PATH
# listen on both a Unix domain socket and a TCP port,
# we use a shorter backlog for quicker failover when busy
listen "/tmp/.sock", :backlog => 64
listen 8080, :tcp_nopush => true
# nuke workers after 30 seconds instead of 60 seconds (the default)
timeout 30
# feel free to point this anywhere accessible on the filesystem
pid APP_PATH + "/tmp/pid/unicorn.pid"
# By default, the Unicorn logger will write to stderr.
# Additionally, ome applications/frameworks log to stderr or stdout,
# so prevent them from going to /dev/null when daemonized here:
stderr_path APP_PATH + "/log/unicorn.stderr.log"
stdout_path APP_PATH + "/log/unicorn.stderr.log"
# combine Ruby 2.0.0dev or REE with "preload_app true" for memory savings
# http://rubyenterpriseedition.com/faq.html#adapt_apps_for_cow
preload_app true
GC.respond_to?(:copy_on_write_friendly=) and
GC.copy_on_write_friendly = true
# Enable this flag to have unicorn test client connections by writing the
# beginning of the HTTP headers before calling the application. This
# prevents calling the application for connections that have disconnected
# while queued. This is only guaranteed to detect clients on the same
# host unicorn runs on, and unlikely to detect disconnects even on a
# fast LAN.
check_client_connection false
before_fork do |server, worker|
# the following is highly recomended for Rails + "preload_app true"
# as there's no need for the master process to hold a connection
defined?(ActiveRecord::Base) and
ActiveRecord::Base.connection.disconnect!
# The following is only recommended for memory/DB-constrained
# installations. It is not needed if your system can house
# twice as many worker_processes as you have configured.
#
# # This allows a new master process to incrementally
# # phase out the old master process with SIGTTOU to avoid a
# # thundering herd (especially in the "preload_app false" case)
# # when doing a transparent upgrade. The last worker spawned
# # will then kill off the old master process with a SIGQUIT.
# old_pid = "#{server.config[:pid]}.oldbin"
# if old_pid != server.pid
# begin
# sig = (worker.nr + 1) >= server.worker_processes ? :QUIT : :TTOU
# Process.kill(sig, File.read(old_pid).to_i)
# rescue Errno::ENOENT, Errno::ESRCH
# end
# end
#
# Throttle the master from forking too quickly by sleeping. Due
# to the implementation of standard Unix signal handlers, this
# helps (but does not completely) prevent identical, repeated signals
# from being lost when the receiving process is busy.
# sleep 1
end
after_fork do |server, worker|
# per-process listener ports for debugging/admin/migrations
# addr = "127.0.0.1:#{9293 + worker.nr}"
# server.listen(addr, :tries => -1, :delay => 5, :tcp_nopush => true)
# the following is *required* for Rails + "preload_app true",
defined?(ActiveRecord::Base) and
ActiveRecord::Base.establish_connection
# if preload_app is true, then you may also want to check and
# restart any other shared sockets/descriptors such as Memcached,
# and Redis. TokyoCabinet file handles are safe to reuse
# between any number of forked children (assuming your kernel
# correctly implements pread()/pwrite() system calls)
end
任何想法可能是什么问题？