Пассажир Phusion: Вы должны использовать Bundler 2 или выше с этим файлом блокировки - PullRequest
0 голосов
/ 26 мая 2019

Я пытаюсь развернуть ROR приложение через nginx и phusion passenger . nginx работает очень хорошо, но я получаю сообщение об ошибке с пассажиром, который запрашивает:

Приложение столкнулось со следующей ошибкой: Вы должны использовать Bundler 2 или больше с этим файлом блокировки. (Bundler :: LockfileError)

Я обновил пакет до версии 2.x, удалил GemFile.lock и снова установил зависимости проекта, но он все еще показывает ту же ошибку. Журналы ошибок приведены ниже.

Error: The application encountered the following error: You must use 

Bundler 2 or greater with this lockfile. (Bundler::LockfileError)
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/bundler/lockfile_parser.rb:108:in `warn_for_outdated_bundler_version'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/bundler/lockfile_parser.rb:95:in `initialize'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/bundler/definition.rb:83:in `new'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/bundler/definition.rb:83:in `initialize'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/bundler/dsl.rb:234:in `new'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/bundler/dsl.rb:234:in `to_definition'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/bundler/dsl.rb:13:in `evaluate'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/bundler/definition.rb:34:in `build'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/bundler.rb:135:in `definition'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/bundler.rb:101:in `setup'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/bundler/setup.rb:20:in `<top (required)>'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:130:in `require'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:130:in `rescue in require'
App 5381 output:     /usr/local/rvm/rubies/ruby-2.5.1/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:34:in `require'
App 5381 output:     /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:363:in `activate_gem'
App 5381 output:     /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:221:in `block in run_load_path_setup_code'
App 5381 output:     /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:527:in `running_bundler'
App 5381 output:     /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:220:in `run_load_path_setup_code'
App 5381 output:     /usr/share/passenger/helper-scripts/rack-preloader.rb:91:in `preload_app'
App 5381 output:     /usr/share/passenger/helper-scripts/rack-preloader.rb:189:in `block in <module:App>'
App 5381 output:     /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:380:in `run_block_and_record_step_progress'
App 5381 output:     /usr/share/passenger/helper-scripts/rack-preloader.rb:188:in `<module:App>'
App 5381 output:     /usr/share/passenger/helper-scripts/rack-preloader.rb:30:in `<module:PhusionPassenger>'
App 5381 output:     /usr/share/passenger/helper-scripts/rack-preloader.rb:29:in `<main>'
[ E 2019-05-26 01:28:17.4084 3842/T1p age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /var/www/html/smsystem-new-ui: The application encountered the following error: You must use Bundler 2 or greater with this lockfile. (Bundler::LockfileError)
  Error ID: 24c7cac4
  Error details saved to: /tmp/passenger-error-fHrekB.html

[ E 2019-05-26 01:28:17.4139 3842/T9 age/Cor/Con/CheckoutSession.cpp:276 ]: [Client 1-8] Cannot checkout session because a spawning error occurred. The identifier of the error is 24c7cac4. Please see earlier logs for details about the error.
...