AWS EC2デプロイができません

Question

ruby on rails でオリジナルアプリを制作しており、EC2でデプロイをしようとしても、エラーが出てうまくいきません。
一応EC2、RDS、S3の設定、EC2への必要なアプリはインストールは終わってます。

bundle exec unicorn_rails -c /var/www/rails/アプリ名/config/unicorn.conf.rb -D -E production
をすると、
master failed to start, check stderr log for details
というエラーが出ます。

unicorn.logを見ると、ative_storage.serviceのエラーとなってるので、S3設定エラーかと思いましたが、現状わかりません。
どのようにしたらエラーを解消できるか教えてもらえると助かります。

log/unicorn.log

I, [2021-07-07T22:00:58.486860 #9852]  INFO -- : Refreshing Gem list
bundler: failed to load command: unicorn_rails (/home/ec2-user/.rbenv/versions/2.7.1/bin/unicorn_rails)
NoMethodError: Cannot load `Rails.config.active_storage.service`:
undefined method `match' for nil:NilClass
  /home/ec2-user/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/aws-partitions-1.472.0/lib/aws-partitions/endpoint_provider.rb:113:in `block in partition_matching_region'
.
.
.
以下省略

config/unicorn.conf.rb

# set lets
  $worker  = 2
  $timeout = 30
  $app_dir = "/var/www/rails/Task_memo"
  $listen  = File.expand_path 'tmp/sockets/.unicorn.sock', $app_dir
  $pid     = File.expand_path 'tmp/pids/unicorn.pid', $app_dir
  $std_log = File.expand_path 'log/unicorn.log', $app_dir
  # set config
  worker_processes  $worker
  working_directory $app_dir
  stderr_path $std_log
  stdout_path $std_log
  timeout $timeout
  listen  $listen
  pid $pid
  # loading booster
  preload_app true
  # before starting processes
  before_fork do |server, worker|
    defined?(ActiveRecord::Base) and ActiveRecord::Base.connection.disconnect!
    old_pid = "#{server.config[:pid]}.oldbin"
    if old_pid != server.pid
      begin
        Process.kill "QUIT", File.read(old_pid).to_i
      rescue Errno::ENOENT, Errno::ESRCH
      end
    end
  end
  # after finishing processes
  after_fork do |server, worker|
    defined?(ActiveRecord::Base) and ActiveRecord::Base.establish_connection
  end

config/storage.yml

test:
  service: Disk
  root: <%= Rails.root.join("tmp/storage") %>

local:
  service: Disk
  root: <%= Rails.root.join("storage") %>

# Use rails credentials:edit to set the AWS secrets (as aws:access_key_id|secret_access_key)
amazon:
  service: S3
  access_key_id: <%= ENV['*******************'] %>
  secret_access_key: <%= ENV['*****************************/***********'] %>
  region: <%= ENV['ap-northeast-1'] %>
  bucket: <%= ENV['my-bucket'] %>
.
.
.
以下省略

database.yml

# PostgreSQL. Versions 9.3 and up are supported.
#
# Install the pg driver:
#   gem install pg
# On macOS with Homebrew:
#   gem install pg -- --with-pg-config=/usr/local/bin/pg_config
# On macOS with MacPorts:
#   gem install pg -- --with-pg-config=/opt/local/lib/postgresql84/bin/pg_config
# On Windows:
#   gem install pg
#       Choose the win32 build.
#       Install PostgreSQL and put its /bin directory on your path.
#
# Configure Using Gemfile
# gem 'pg'
#
default: &default
  adapter: postgresql

  encoding: unicode
  # For details on connection pooling, see Rails configuration guide
  # https://guides.rubyonrails.org/configuring.html#database-pooling
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>

development:
  <<: *default
  database: memo_development

  # The specified database role being used to connect to postgres.
  # To create additional roles in postgres see `$ createuser --help`.
  # When left blank, postgres will use the default role. This is
  # the same name as the operating system user that initialized the database.
  #username: memo

  # The password associated with the postgres role (username).
  #password:

  # Connect on a TCP socket. Omitted by default since the client uses a
  # domain socket that doesn't need configuration. Windows does not have
  # domain sockets, so uncomment these lines.
  host: localhost

  # The TCP port the server listens on. Defaults to 5432.
  # If your server runs on a different port number, change accordingly.
  port: 5432

  # Schema search path. The server defaults to $user,public
  #schema_search_path: myapp,sharedapp,public

  # Minimum log levels, in increasing order:
#   debug5, debug4, debug3, debug2, debug1,
  #   log, notice, warning, error, fatal, and panic
  # Defaults to warning.
  #min_messages: notice

# 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: memo_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="postgres://myuser:mypass@localhost/somedatabase"
#
# You can use this database configuration with:
#
#   production:
#     url: <%= ENV['DATABASE_URL'] %>
#
production:
  <<: *default
  adapter: postgresql
  encoding: unicode
  # For details on connection pooling, see Rails configuration guide
  # https://railsguides.jp/configuring.html#データベース接続をプールする
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
  database: <%= ENV['DB_NAME'] %>
  username: <%= ENV['DB_USERNAME'] %>
  password: <%= ENV['DB_PASSWORD'] %>
  host: <%= ENV['DB_HOST'] %>

Comments

[fukasawah]

Railsは全く分からないのですが、config/storage.ymlのENVを使うのは正しいのでしょうか？

active_storageではそのような使い方にはなってなさそうに見えます。
https://edgeguides.rubyonrails.org/active_storage_overview.html

なんとなくですが、ENVにそのようなキーがないので空文字列で処理されてる気がしました。

単純に以下のようにするのではだめなんでしょうか？

```
amazon:
service: S3
access_key_id: '*******************'
secret_access_key: '*****************************/***********'
region: 'ap-northeast-1'
bucket: 'my-bucket'
```

[kol2122]

返信が遅くなり申し訳ございません。
無事デプロイできました。