ruby-on-rails - Phusion Passenger 未启动 - flock':没有可用的锁 @ rb_file_flock -/vagrant/tmp/pids/passenger.3000.pid.lock (Errno::ENOLCK)

Question

这是一个在 Phusion Passenger 上运行的 Rails 应用。

在开发环境(乘客独立模式)中，我在基于 Vagrant Ubuntu 14.04 的机器上运行它，在 MBP(工作)和 Linux Mint PC(家用)中。

在 gemfile 中:gem 'passenger'

根据我的 Gemfile.lock，现在它位于 passenger (5.0.25)。

我通常用来启动 Rails 服务器的命令是 Procfile 中的 passenger start。

rails: passenger start
sidekiq: bundle exec sidekiq

在我的家用 PC 中，当我发出命令 foreman start 或 passenger start 我得到:

/home/vagrant/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.25/src/ruby_supportlib/phusion_passenger/vendor/daemon_controller/lock_file.rb:67:in `flock': No locks available @ rb_file_flock - /vagrant/tmp/pids/passenger.3000.pid.lock (Errno::ENOLCK)
    from /home/vagrant/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.25/src/ruby_supportlib/phusion_passenger/vendor/daemon_controller/lock_file.rb:67:in `block in exclusive_lock'
    from /home/vagrant/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.25/src/ruby_supportlib/phusion_passenger/vendor/daemon_controller/lock_file.rb:63:in `open'
    from /home/vagrant/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.25/src/ruby_supportlib/phusion_passenger/vendor/daemon_controller/lock_file.rb:63:in `exclusive_lock'
    from /home/vagrant/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.25/src/ruby_supportlib/phusion_passenger/vendor/daemon_controller.rb:219:in `start'
    from /home/vagrant/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.25/src/ruby_supportlib/phusion_passenger/standalone/start_command/nginx_engine.rb:49:in `start_engine_real'
    from /home/vagrant/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.25/src/ruby_supportlib/phusion_passenger/standalone/start_command.rb:322:in `start_engine'
    from /home/vagrant/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.25/src/ruby_supportlib/phusion_passenger/standalone/start_command.rb:63:in `run'
    from /home/vagrant/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.25/src/ruby_supportlib/phusion_passenger/standalone/main.rb:51:in `run!'
    from /home/vagrant/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.25/bin/passenger:45:in `<top (required)>'
    from /home/vagrant/ruby/bin/passenger:23:in `load'
    from /home/vagrant/ruby/bin/passenger:23:in `<main>'

当我使用命令 passenger-config restart-app 我得到:

*** ERROR: Phusion Passenger doesn't seem to be running. If you are sure that it
is running, then the causes of this problem could be one of:

 1. You customized the instance registry directory using Apache's
    PassengerInstanceRegistryDir option, Nginx's
    passenger_instance_registry_dir option, or Phusion Passenger Standalone's
    --instance-registry-dir command line argument. If so, please set the
    environment variable PASSENGER_INSTANCE_REGISTRY_DIR to that directory
    and run this command again.
 2. The instance directory has been removed by an operating system background
    service. Please set a different instance registry directory using Apache's
    PassengerInstanceRegistryDir option, Nginx's passenger_instance_registry_dir
    option, or Phusion Passenger Standalone's --instance-registry-dir command
    line argument.

Env var PASSENGER_INSTANCE_REGISTRY_DIR 未设置，所以 following passenger's documentation我尝试将其设置为:

export PASSENGER_INSTANCE_REGISTRY_DIR=/vagrant/tmp 或 export PASSENGER_INSTANCE_REGISTRY_DIR=tmp

然后

sudo -E passenger-status 但有了这个我得到 sudo: passenger-status: command not found

根据 Hongli's answer在另一个具有类似情况的线程中，命令 sudo env PASSENGER_INSTANCE_REGISTRY_DIR=/tmp passenger-status 返回:

env: passenger-status: No such file or directory

最后，在我的 rails app tmp 文件夹中有 passenger pid 文件:

• passenger.3000.pid
• passenger.3000.pid.lock

我真的是一窍不通。没有日志，我搜索和发现的所有内容都没有解决这个问题。

感谢您的帮助!

Answer 1

能否请您尝试在另一个港口开始乘客并检查问题是否仍然存在。

乘客开始-p 3001