前提
Ruby on Rails6にてアプリを作成
AWS amazon linux2
デプロイ作業を行いました
実現したいこと
本番環境でRailsを起動させたい
発生している問題・エラーメッセージ
ターミナル
[ec2-user@********** Dr_tetsu]$ less log/unicorn.stderr.log
I, [2020-12-07T06:03:34.092137 #12835] INFO -- : Refreshing Gem list
I, [2020-12-07T06:03:36.545685 #12835] INFO -- : listening on addr=0.0.0.0:3000 fd=11
E, [2020-12-07T06:03:36.546263 #12835] ERROR -- : Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) (Mysql2::Error::ConnectionError)
/home/ec2-user/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/mysql2-0.5.3/lib/mysql2/client.rb:90:in `connect'
/home/ec2-user/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/mysql2-0.5.3/lib/mysql2/client.rb:90:in `initialize'
/home/ec2-user/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/mysql2_adapter.rb:24:in `new'
/home/ec2-user/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/mysql2_adapter.rb:24:in `mysql2_connection'
/home/ec2-user/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:887:in `new_connection'
/home/ec2-user/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:931:in `checkout_new_connection'
/home/ec2-user/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:910:in `try_to_checkout_new_connection'
該当するソースコード
database.yml
# MySQL. Versions 5.5.8 and up are supported.
#
# Install the MySQL driver
# gem install mysql2
#
# Ensure the MySQL gem is defined in your Gemfile
# gem 'mysql2'
#
# And be sure to use new-style password hashing:
# https://dev.mysql.com/doc/refman/5.7/en/password-hashing.html
#
default: &default
adapter: mysql2
encoding: utf8mb4
pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
username: root
password: kenichi1203
socket: /tmp/mysql.sock
development:
<<: *default
database: Dr_tetsu_development
# Warning: The database defined as "test" will be erased and
# re-generated from your development database when you run "rake".
# Do not set this db to the same as development or production.
test:
<<: *default
database: Dr_tetsu_test
# As with config/credentials.yml, you never want to store sensitive information,
# like your database password, in your source code. If your source code is
# ever seen by anyone, they now have access to your database.
#
# Instead, provide the password as a unix environment variable when you boot
# the app. Read https://guides.rubyonrails.org/configuring.html#configuring-a-database
# for a full rundown on how to provide these environment variables in a
# production deployment.
#
# On Heroku and other platform providers, you may have a full connection URL
# available as an environment variable. For example:
#
# DATABASE_URL="mysql2://myuser:mypass@localhost/somedatabase"
#
# You can use this database configuration with:
#
# production:
# url: <%= ENV['DATABASE_URL'] %>
#
production:
<<: *default
database: Dr_tetsu_production
username: root
password: <%= ENV['DATABASE_PASSWORD'] %>
socket: /var/lib/mysql/mysql.sock
試したこと（仮説）
ERROR -- : Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
/log/unicorn.stderr.log
/home/ec2-user/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/unicorn-5.4.1/lib/unicorn/http_server.rb:205:in `pid=': Already running on PID:18695 (or pid=/var/www/Dr_tetsu/tmp/pids/unicorn.pid is stale) (ArgumentError)
from /home/ec2-user/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/unicorn-5.4.1/lib/unicorn/http_server.rb:137:in `start'
from /home/ec2-user/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/unicorn-5.4.1/bin/unicorn_rails:209:in `<top (required)>'
from /home/ec2-user/.rbenv/versions/2.5.1/bin/unicorn_rails:23:in `load'
from /home/ec2-user/.rbenv/versions/2.5.1/bin/unicorn_rails:23:in `<main>'
I, [2020-12-10T06:22:53.949207 #18695] INFO -- : reaped #<Process::Status: pid 18699 exit 0> worker=0
I, [2020-12-10T06:22:53.949342 #18695] INFO -- : master complete
I, [2020-12-10T06:22:57.328776 #18777] INFO -- : Refreshing Gem list
I, [2020-12-10T06:22:58.956594 #18777] INFO -- : listening on addr=0.0.0.0:3000 fd=11
I, [2020-12-10T06:22:58.962392 #18777] INFO -- : master process ready
I, [2020-12-10T06:22:58.967624 #18781] INFO -- : worker=0 ready
I, [2020-12-10T06:25:16.316706 #18777] INFO -- : reaped #<Process::Status: pid 18781 exit 0> worker=0
I, [2020-12-10T06:25:16.316854 #18777] INFO -- : master complete
I, [2020-12-10T06:25:50.238430 #18956] INFO -- : Refreshing Gem list
I, [2020-12-10T06:25:51.895253 #18956] INFO -- : listening on addr=0.0.0.0:3000 fd=11
I, [2020-12-10T06:25:51.901216 #18956] INFO -- : master process ready
:
yu_1985様
ご返信ありがとうございます！
ec2-user@************ Dr_tetsu$ sudo systemctl status mysql
Unit mysql.service could not be found.
と表示されました。
ec2-user@*************Dr_tetsu$ sudo service mysqld start
Redirecting to /bin/systemctl start mysqld.service
と表示されます。
はい。前回ご教示頂いたことを調べながら熟読させて頂きましたがまだ理解に苦しんでいるのが現状です。申し訳ありません。
正しいかどうかは自分がどうしたいかによるのですが…。
すべての環境の設定が同じなのですが、それは意図通りですか？
パスワードは環境変数で各環境ごとに変えるならdefaultに書いてしまってもいいでしょう。
もとはdefaultは直書きでしたよね。
いっそのこと、すべて環境変数にしてしまってdatabase,ymlにはdefaultだけ書いて、環境変数で値をコントロールする、というのも一つの方法です。
ちなみに、エラーの内容が
> Can't connect to local MySQL server through socket '/tmp/mysql.sock'
だったので、元の設定だとdafaultに定義していたsocketの設定を参照してしまっていたであろうことが想像できます。
yu_1985様
mysql> show global variables like 'character%';
+--------------------------+----------------------------+
| Variable_name | Value |
+--------------------------+----------------------------+
| character_set_client | latin1 |
| character_set_connection | latin1 |
| character_set_database | latin1 |
| character_set_filesystem | binary |
| character_set_results | latin1 |
| character_set_server | latin1 |
| character_set_system | utf8 |
| character_sets_dir | /usr/share/mysql/charsets/ |
+--------------------------+----------------------------+
8 rows in set (0.01 sec)
mysql> exit
Bye
[ec2-user@********* Dr_tetsu]$ sudo vi /etc/my.cnf
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
となりました！
yu_1985様
ご返信ありがとうございます！
＞unicornを立ち上げる前に既存のunicornのプロセスをkillしてください
killを実行しましたが本番環境でWe're sorry, but something went wrong.
が表示されます。再度、/log/unicorn.stderr.logを確認すると補足２のようになりました。
Q&A
