【Rails】Pumaが起動出来ない問題

Question

EC2にデプロイを終え、いざ、pumaを起動するために、
bundle exec pumaを実行したところ以下のエラーに遭遇しました。

  sample git:(master) bundle exec puma
Puma starting in single mode...
* Version 3.7.0 (ruby 2.4.1-p111), codename: Snowy Sagebrush
* Min threads: 5, max threads: 5
* Environment: production
/home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/xml_mini.rb:51: warning: constant ::Fixnum is deprecated
/home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/xml_mini.rb:52: warning: constant ::Bignum is deprecated
/home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activesupport-5.0.1/lib/active_support/core_ext/numeric/conversions.rb:138: warning: constant ::Fixnum is deprecated
/home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activejob-5.0.1/lib/active_job/arguments.rb:38: warning: constant ::Fixnum is deprecated
/home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activejob-5.0.1/lib/active_job/arguments.rb:38: warning: constant ::Bignum is deprecated
* Listening on tcp://0.0.0.0:3000
* Listening on unix:///var/www/rails/sample/tmp/sockets/puma.sock
bundler: failed to load command: puma (/home/sample/.rbenv/versions/2.4.1/bin/puma)
Errno::ENOENT: No such file or directory - connect(2) for /var/www/rails/sample/tmp/sockets/puma.sock
  /home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/puma-3.7.0/lib/puma/binder.rb:366:in `initialize'
  /home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/puma-3.7.0/lib/puma/binder.rb:366:in `new'
  /home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/puma-3.7.0/lib/puma/binder.rb:366:in `add_unix_listener'
  /home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/puma-3.7.0/lib/puma/binder.rb:141:in `block in parse'
  /home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/puma-3.7.0/lib/puma/binder.rb:88:in `each'
  /home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/puma-3.7.0/lib/puma/binder.rb:88:in `parse'
  /home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/puma-3.7.0/lib/puma/runner.rb:144:in `load_and_bind'
  /home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/puma-3.7.0/lib/puma/single.rb:87:in `run'
  /home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/puma-3.7.0/lib/puma/launcher.rb:171:in `run'
  /home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/puma-3.7.0/lib/puma/cli.rb:77:in `run'
  /home/sample/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/puma-3.7.0/bin/puma:10:in `<top (required)>'
  /home/sample/.rbenv/versions/2.4.1/bin/puma:22:in `load'
  /home/sample/.rbenv/versions/2.4.1/bin/puma:22:in `<top (required)>'

/config/puma.rbの設定は以下の通りです。

threads_count = ENV.fetch("RAILS_MAX_THREADS") { 5 }.to_i
threads threads_count, threads_count

# Specifies the `port` that Puma will listen on to receive requests, default is 3000.
#
port        ENV.fetch("PORT") { 3000 }

# Specifies the `environment` that Puma will run in.
#
environment ENV.fetch("RAILS_ENV") { "production" }

# Allow puma to be restarted by `rails restart` command.
plugin :tmp_restart

app_root = File.expand_path("../..",__FILE__)
bind "unix://#{app_root}/tmp/sockets/puma.sock"
pidfile "#{app_root}/tmp/pids/puma.pid"
state_path "#{app_root}/tmp/pids/puma.state"
# daemonize true

エラーの通り、確かに、/var/www/rails/sample/tmp/socketsにpuma.sockというファイルが生成されていませんでした。

これは自分で手動で作成しなければいけないのでしょうか？？
以前別のrailsアプリをデプロイした際には手動で作成した記憶がなく、何か他に問題があるのかな？とは思うのですが・・・。

お分かりになりましたら、教えて頂けると幸いです！

Answer 1

自分でディレクトリを作成すると、エラーなく起動出来ました。

cd /var/www/rails/sample/tmp
mkdir sockets