現在、railsでポートフォリを作成中ですが、エラーが出て詰まっています bundle exec cap production deployとうつとエラーが出ます。 bundle exec cap production deploy --dry-runではエラーが出ずにうまくいきます。 (Capistrano編)世界一丁寧なAWS解説。EC2を利用して、RailsアプリをAWSにあげるまで
基本的にはこれを軸に進めています。
発生している問題・エラーメッセージ
00:15 unicorn:restart
01 $HOME/.rbenv/bin/rbenv exec bundle exec unicorn -c /var/www/Oekaki_app/current/config/unicorn/production.rb -E production -D
01 master failed to start, check stderr log for details
#<Thread:0x00007fb997b8f328@/Users/sugiuraeiosamu/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sshkit-1.20.0/lib/sshkit/runners/parallel.rb:10 run> terminated with exception (report_on_exception is true):
Traceback (most recent call last):
1: from /Users/sugiuraeiosamu/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sshkit-1.20.0/lib/sshkit/runners/parallel.rb:11:in `block (2 levels) in execute'
/Users/sugiuraeiosamu/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sshkit-1.20.0/lib/sshkit/runners/parallel.rb:15:in `rescue in block (2 levels) in execute': Exception while executing as ec2-user@18.177.63.188: bundle exit status: 1 (SSHKit::Runner::ExecuteError)
bundle stdout: Nothing written
bundle stderr: master failed to start, check stderr log for details
#<Thread:0x00007fb997b9d9a0@/Users/sugiuraeiosamu/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sshkit-1.20.0/lib/sshkit/runners/parallel.rb:10 run> terminated with exception (report_on_exception is true):
Traceback (most recent call last):
1: from /Users/sugiuraeiosamu/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sshkit-1.20.0/lib/sshkit/runners/parallel.rb:11:in `block (2 levels) in execute'
/Users/sugiuraeiosamu/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sshkit-1.20.0/lib/sshkit/runners/parallel.rb:15:in `rescue in block (2 levels) in execute': Exception while executing as ec2-user@18.177.63.188: Exception while executing as ec2-user@18.177.63.188: bundle exit status: 1 (SSHKit::Runner::ExecuteError)
bundle stdout: Nothing written
bundle stderr: master failed to start, check stderr log for details
(Backtrace restricted to imported tasks)
cap aborted!
SSHKit::Runner::ExecuteError: Exception while executing as ec2-user@18.177.63.188: Exception while executing as ec2-user@18.177.63.188: bundle exit status: 1
bundle stdout: Nothing written
bundle stderr: master failed to start, check stderr log for details
Caused by:
SSHKit::Runner::ExecuteError: Exception while executing as ec2-user@18.177.63.188: bundle exit status: 1
bundle stdout: Nothing written
bundle stderr: master failed to start, check stderr log for details
Caused by:
SSHKit::Command::Failed: bundle exit status: 1
bundle stdout: Nothing written
bundle stderr: master failed to start, check stderr log for details
/Users/sugiuraeiosamu/environment/Oekaki_app/lib/capistrano/tasks/unicorn.rb:11:in `block in start_unicorn'
/Users/sugiuraeiosamu/environment/Oekaki_app/lib/capistrano/tasks/unicorn.rb:10:in `start_unicorn'
/Users/sugiuraeiosamu/environment/Oekaki_app/lib/capistrano/tasks/unicorn.rb:47:in `block (3 levels) in <top (required)>'
Tasks: TOP => deploy:restart
(See full trace by running task with --trace)
The deploy has failed with an error: Exception while executing as ec2-user@18.177.63.188: Exception while executing as ec2-user@18.177.63.188: bundle exit status: 1
bundle stdout: Nothing written
bundle stderr: master failed to start, check stderr log for details
Gemfile
source 'https://rubygems.org'
git_source(:github) { |repo| "https://github.com/#{repo}.git" }
ruby '2.5.1'
# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '~> 5.2.3'
# Use postgresql as the database for Active Record
gem 'pg', '>= 0.18', '< 2.0'
# Use Puma as the app server
gem 'puma', '~> 3.11'
# Use SCSS for stylesheets
gem 'sass-rails', '~> 5.0'
# Use Uglifier as compressor for JavaScript assets
gem 'uglifier', '>= 1.3.0'
# See https://github.com/rails/execjs#readme for more supported runtimes
# gem 'mini_racer', platforms: :ruby
# Use CoffeeScript for .coffee assets and views
gem 'coffee-rails', '~> 4.2'
# Turbolinks makes navigating your web application faster. Read more: https://github.com/turbolinks/turbolinks
gem 'turbolinks', '~> 5'
# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
gem 'jbuilder', '~> 2.5'
# Use Redis adapter to run Action Cable in production
# gem 'redis', '~> 4.0'
# Use ActiveModel has_secure_password
# gem 'bcrypt', '~> 3.1.7'
# Use ActiveStorage variant
# gem 'mini_magick', '~> 4.8'
# Use Capistrano for deployment
# gem 'capistrano-rails', group: :development
# Reduces boot times through caching; required in config/boot.rb
gem 'bootsnap', '>= 1.1.0', require: false
group :development, :test do
# Call 'byebug' anywhere in the code to stop execution and get a debugger console
gem 'byebug', platforms: [:mri, :mingw, :x64_mingw]
gem 'rspec-rails'
gem 'factory_bot_rails'
gem 'hirb'
gem 'hirb-unicode'
gem 'dotenv-rails'
gem 'capistrano'
gem 'capistrano-bundler'
gem 'capistrano-rails'
gem 'capistrano-rbenv'
end
group :production, :staging do
gem 'unicorn'
end
group :development do
# Access an interactive console on exception pages or by calling 'console' anywhere in the code.
gem 'web-console', '>= 3.3.0'
gem 'listen', '>= 3.0.5', '< 3.2'
# Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
gem 'spring'
gem 'spring-watcher-listen', '~> 2.0.0'
end
group :test do
# Adds support for Capybara system testing and selenium driver
gem 'capybara', '>= 2.15'
# Easy installation and use of chromedriver to run system tests with Chrome
# gem 'chromedriver-helper'
gem 'webdrivers'
gem 'selenium-webdriver'
end
# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]
gem 'slim-rails'
gem 'html2slim'
gem "bootstrap", "~> 4.3.1"
gem 'jquery-rails'
gem 'shrine'
gem 'devise'
gem 'devise-i18n'
gem 'devise-i18n-views'
gem 'image_processing'
gem 'mini_magick'
gem 'font-awesome-sass'
gem "aws-sdk-s3", require: false
gem 'omniauth'
gem 'omniauth-twitter'
##追記２
unicorn側とnginx側のsockが違っていて治して、更にサーバー側からunicornをkillしたら、最後まで'bundle exec cap production deployが最後までできましたが。 ①サーバー側にインターネットからアクセスすると４０３エラーになります。 ②また、bundle exec cap production deploy`をunicornをkillせずにやると追記１と同じエラーが出ます。 Unicornの古いプロセスが消えません
今はこれが気になります。
できました。
４０３エラーはlog/nginx.error.log から権限の確認で解決できます。
追記３の①はスルーで問題ない感じです。
②はやはりできません。手動でunicornをサーバー上で切るとまたbundle exec cap production deployが最後までエラーなくできます。
Q&A
バッドをするには、ログインかつ
こちらの条件を満たす必要があります。
2019/11/29 19:43