capistrano / rails

Official Ruby on Rails specific tasks for Capistrano
http://www.capistranorb.com/
MIT License
867 stars 270 forks source link

I met a question cap production deploy Report an error DEPLOY FAILED #229

Closed AlZero-t closed 5 years ago

AlZero-t commented 5 years ago

DEPLOY FAILED Refer to log/capistrano.log for details. Here are the last 20 lines:

INFO [831600aa] Finished in 0.055 seconds with exit status 0 (successful).

DEBUG [74dd732d] Running [ -L /home/ywserver/webapps/prototype_new/releases/20181128054845/public/assets ] as root@192.168.2.100

DEBUG [74dd732d] Command: [ -L /home/ywserver/webapps/prototype_new/releases/20181128054845/public/assets ]

DEBUG [9680fd8d] Finished in 0.055 seconds with exit status 1 (failed).

DEBUG [fae4947b] Running [ -d /home/ywserver/webapps/prototype_new/releases/20181128054845/public/assets ] as root@192.168.2.100

DEBUG [fae4947b] Command: [ -d /home/ywserver/webapps/prototype_new/releases/20181128054845/public/assets ]

DEBUG [a7a5cd4d] Finished in 0.051 seconds with exit status 1 (failed).

INFO [9d3dbfa5] Running /usr/bin/env ln -s /home/ywserver/webapps/prototype_new/shared/public/assets /home/ywserver/webapps/prototype_new/releases/20181128054845/public/assets as root@192.168.2.100

DEBUG [9d3dbfa5] Command: ( export PATH="/home/ywserver/usr/local/ruby/bin:$PATH" ; /usr/bin/env ln -s /home/ywserver/webapps/prototype_new/shared/public/assets /home/ywserver/webapps/prototype_new/releases/20181128054845/public/assets )

INFO [72702029] Finished in 0.077 seconds with exit status 0 (successful).

DEBUG [4ce76c4b] Running if test ! -d /home/ywserver/webapps/prototype_new/releases/20181128054845; then echo "Directory does not exist '/home/ywserver/webapps/prototype_new/releases/20181128054845'" 1>&2; false; fi as root@192.168.2.100

DEBUG [4ce76c4b] Command: if test ! -d /home/ywserver/webapps/prototype_new/releases/20181128054845; then echo "Directory does not exist '/home/ywserver/webapps/prototype_new/releases/20181128054845'" 1>&2; false; fi

DEBUG [7dbcda90] Finished in 0.051 seconds with exit status 0 (successful).

DEBUG [c511405a] Running /usr/bin/env bundle check --path /home/ywserver/webapps/prototype_new/shared/bundle as root@192.168.2.100

DEBUG [c511405a] Command: cd /home/ywserver/webapps/prototype_new/releases/20181128054845 && ( export PATH="/home/ywserver/usr/local/ruby/bin:$PATH" ; /usr/bin/env bundle check --path /home/ywserver/webapps/prototype_new/shared/bundle )

DEBUG [2324633e] /usr/bin/env: bundle: No such file or directory

DEBUG [2324633e] Finished in 0.050 seconds with exit status 127 (failed).

INFO [15bd5f2c] Running /usr/bin/env bundle install --path /home/ywserver/webapps/prototype_new/shared/bundle --without development test --deployment --quiet as root@192.168.2.100

DEBUG [15bd5f2c] Command: cd /home/ywserver/webapps/prototype_new/releases/20181128054845 && ( export PATH="/home/ywserver/usr/local/ruby/bin:$PATH" ; /usr/bin/env bundle install --path /home/ywserver/webapps/prototype_new/shared/bundle --without development test --deployment --quiet )

DEBUG [a1a40dd8] /usr/bin/env: bundle: No such file or directory

00:11 sidekiq:start 01 bundle exec sidekiq --index 0 --pidfile /home/ywserver/webapps/prototype_new/shared/tmp/pids/sidekiq-0.pid --environment production --logfile /home/ywserver/webapps/prototype_new/shared/log/sidekiq.log --daemon 01 bash: bundle: command not found /root/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/sshkit-1.18.0/lib/sshkit/runners/parallel.rb:15:in rescue in block (2 levels) in execute': Exception while executing as root@192.168.2.100: sidekiq exit status: 127 (SSHKit::Runner::ExecuteError) sidekiq stdout: Nothing written sidekiq stderr: bash: bundle: command not found from /root/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/sshkit-1.18.0/lib/sshkit/runners/parallel.rb:11:inblock (2 levels) in execute'

mattbrictson commented 5 years ago

Hi, sorry for the late reply. I hope you figured out a solution! In the future I recommend directing this kind of support question to Stack Overflow, where you are more likely to get timely feedback. The issue tracker on GitHub is low traffic and used primarily for bug reports and feature requests, not for support.

If you've found what seems like a bug in capistrano or capistrano-rails please reopen this or submit a new ticket. Thanks!