rails4.2 herokuデプロイ後のNo such file or directory - ./log/sidekiq.log

Question

herokuにデプロイ下後にログを確認すると
No such file or directory - ./log/sidekiq.logとなります。

procfileに書いたコードが正しく動いていません
プロセスを確認したらクラッシュしています。構成はheroku sidekiqです。

worker: bundle exec sidekiq -q carrierwave

#config/initializers/sidkiq.rb
Sidekiq.configure_server do |config|
  case Rails.env
    when 'production' then
      config.redis = { url: ENV['REDISCLOUD_URL'], namespace: 'sidekiq' }
    when 'staging' then
      config.redis = { url: 'redis://stg.redis-example.com:6379', namespace: 'sidekiq' }
    else
      config.redis = { url: 'redis://localhost:6379', namespace: 'sidekiq' }
  end
end

Sidekiq.configure_client do |config|
  case Rails.env
    when 'production' then
      config.redis = { url: ENV['REDISCLOUD_URL'], namespace: 'sidekiq' }
    when 'staging' then
      config.redis = { url: 'redis://stg.redis-example.com:6379', namespace: 'sidekiq' }
    else
      config.redis = { url: 'redis://localhost:6379', namespace: 'sidekiq' }
  end
end


# heroku ps
=== web (Free): `bin/rails server -p $PORT -e $RAILS_ENV`
web.1: up 2015/07/18 18:17:11 (~ 7m ago)

=== worker (Free): `bundle exec sidekiq -q carrierwave`
worker.1: crashed 2015/07/18 18:17:00 (~ 7m ago)



#ログ

2015-07-18T10:23:42.061270+00:00 heroku[slug-compiler]: Slug compilation started
2015-07-18T10:23:42.061295+00:00 heroku[slug-compiler]: Slug compilation finished
2015-07-18T10:23:42.021143+00:00 heroku[api]: Deploy f93ebd5 by [e-mail]
2015-07-18T10:23:42.021143+00:00 heroku[api]: Release v21 created by [e-mail]
2015-07-18T10:23:42.123744+00:00 heroku[web.1]: State changed from up to starting
2015-07-18T10:23:42.177341+00:00 heroku[worker.1]: State changed from crashed to starting
2015-07-18T10:23:44.617806+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2015-07-18T10:23:45.267925+00:00 app[web.1]: [2015-07-18 10:23:45] FATAL SignalException: SIGTERM
2015-07-18T10:23:45.267930+00:00 app[web.1]:    /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:170:in `select'
2015-07-18T10:23:45.267934+00:00 app[web.1]:    /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:170:in `block in start'
2015-07-18T10:23:45.267935+00:00 app[web.1]:    /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:32:in `start'
2015-07-18T10:23:45.267937+00:00 app[web.1]:    /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:160:in `start'
2015-07-18T10:23:45.267938+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/handler/webrick.rb:34:in `run'
2015-07-18T10:23:45.267940+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/server.rb:286:in `start'
2015-07-18T10:23:45.267942+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/commands/server.rb:80:in `start'
2015-07-18T10:23:45.267944+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/commands/commands_tasks.rb:80:in `block in server'
2015-07-18T10:23:45.267945+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/commands/commands_tasks.rb:75:in `tap'
2015-07-18T10:23:45.267947+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/commands/commands_tasks.rb:75:in `server'
2015-07-18T10:23:45.267948+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
2015-07-18T10:23:45.267949+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/railties-4.2.0/lib/rails/commands.rb:17:in `<top (required)>'
2015-07-18T10:23:45.267951+00:00 app[web.1]:    bin/rails:4:in `require'
2015-07-18T10:23:45.267953+00:00 app[web.1]:    bin/rails:4:in `<main>'
2015-07-18T10:23:45.267959+00:00 app[web.1]: [2015-07-18 10:23:45] INFO  going to shutdown ...
2015-07-18T10:23:45.267990+00:00 app[web.1]: [2015-07-18 10:23:45] INFO  WEBrick::HTTPServer#start done.
2015-07-18T10:23:45.268011+00:00 app[web.1]: Exiting
2015-07-18T10:23:46.415651+00:00 heroku[web.1]: Process exited with status 143
2015-07-18T10:23:47.535914+00:00 heroku[worker.1]: Starting process with command `bundle exec sidekiq -q carrierwave`
2015-07-18T10:23:48.098136+00:00 heroku[worker.1]: State changed from starting to up
2015-07-18T10:23:50.030358+00:00 app[worker.1]: No such file or directory - ./log/sidekiq.log
2015-07-18T10:23:50.030383+00:00 app[worker.1]: /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/logger.rb:601:in `initialize'
2015-07-18T10:23:50.030385+00:00 app[worker.1]: /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/logger.rb:601:in `open'
2015-07-18T10:23:50.030386+00:00 app[worker.1]: /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/logger.rb:601:in `create_logfile'
2015-07-18T10:23:50.030387+00:00 app[worker.1]: /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/logger.rb:596:in `open_logfile'
2015-07-18T10:23:50.030388+00:00 app[worker.1]: /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/logger.rb:551:in `initialize'
2015-07-18T10:23:50.030389+00:00 app[worker.1]: /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/logger.rb:318:in `new'
2015-07-18T10:23:50.030390+00:00 app[worker.1]: /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/logger.rb:318:in `initialize'
2015-07-18T10:23:50.030391+00:00 app[worker.1]: /app/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/logging.rb:31:in `new'
2015-07-18T10:23:50.030393+00:00 app[worker.1]: /app/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/logging.rb:31:in `initialize_logger'
2015-07-18T10:23:50.030394+00:00 app[worker.1]: /app/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/cli.rb:344:in `initialize_logger'
2015-07-18T10:23:50.030395+00:00 app[worker.1]: /app/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/cli.rb:39:in `parse'
2015-07-18T10:23:50.030396+00:00 app[worker.1]: /app/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/bin/sidekiq:7:in `<top (required)>'
2015-07-18T10:23:50.030397+00:00 app[worker.1]: /app/vendor/bundle/ruby/2.0.0/bin/sidekiq:23:in `load'
2015-07-18T10:23:50.030398+00:00 app[worker.1]: /app/vendor/bundle/ruby/2.0.0/bin/sidekiq:23:in `<main>'
2015-07-18T10:23:50.723134+00:00 heroku[worker.1]: State changed from up to crashed
2015-07-18T10:23:50.712026+00:00 heroku[worker.1]: Process exited with status 1
2015-07-18T10:23:52.176177+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 46937 -e production`
2015-07-18T10:24:04.392037+00:00 heroku[web.1]: State changed from starting to up
2015-07-18T10:24:04.241645+00:00 app[web.1]: [2015-07-18 10:24:04] INFO  WEBrick 1.3.1
2015-07-18T10:24:04.241670+00:00 app[web.1]: [2015-07-18 10:24:04] INFO  ruby 2.0.0 (2015-04-13) [x86_64-linux]
2015-07-18T10:24:04.242017+00:00 app[web.1]: [2015-07-18 10:24:04] INFO  WEBrick::HTTPServer#start: pid=3 port=46937

Answer 1

No such file or directory - ./log/sidekiq.log

とあるので、なんらかのタイミングで空のsidekiq.logをlogに含めてはいかがでしょうか

touch log/sidekiq.log
git add log/sidekiq.log

Procfile:

worker: touch log/sidekiq.log; bundle exec sidekiq -q ....

あるいはログを吐く場所の明示や、sidekiq.yml に設定を書き込むなどする方法もあるかもしれません

bundle exec sidekiq -d -L log/sidekiq.log -C config/sidekiq.yml -e production
-d, Daemonize process
-L, path to writable logfile
-C, path to YAML config file
-e, Application environment

• ruby on rails - How to run sidekiq in production server? - Stack Overflow

簡単に調べてみましたが、何か参考になれば幸いです

Link

• ruby on rails - How to run sidekiq in production server? - Stack Overflow
• sidekiq/config.yml at master · mperham/sidekiq - GitHub
• Logging · mperham/sidekiq Wiki - GitHub
• Rails - herokuでsidekiq起動時のエラー対処方法 - Qiita