$ bundle exec cap production deploy
(Backtrace restricted to imported tasks) cap aborted!
SSHKit::Runner::ExecuteError:
Exception while executing as Psara@sakura: git exit status: 128 git stdout: Nothing written git
stderr: Permission denied (publickey).
fatal: The remote end hung up unexpectedly
SSHKit::Command::Failed:
git exit status: 128
git stdout:Nothing written
git stderr: Permission denied (publickey).
fatal: The remote end hung up unexpectedly
Tasks: TOP => git:check (See full trace by running task with --trace)
The deploy has failed with an error:
Exception while executing as Psara@sakura:
git exit status: 128 git stdout: Nothing written
git stderr: Permission denied (publickey).
fatal: The remote end hung up unexpectedly
*
deploy.rb
set :application, 'Psara'
set :repo_url, 'git@bitbucket.org:CBLaughter/psara.git'
set :deploy_to, '/home/Psara/Psara'
set :default_run_options, :pty => true
namespace :deploy do
after :restart, :clear_cache do
on roles(:web), in: :groups, limit: 3, wait: 10 do
# Here we can do anything such as:
# within release_path do
# execute :rake, 'cache:clear'
# end
end end
end
set :ssh_options, { forward_agent: true, paranoid: true, keys:
"~/.ssh/id_rsa" }
*
production.rb
set :stage, :staging
set :rails_env, :production
role :app, %w{sakura}
role :web, %w{sakura}
role :db, %w{sakura}
server 'sakura', user: 'Psara', roles: %w{web app}, my_property: >:my_value
set :ssh_options, {
keys: %w(~/.ssh/id_rsa),
forward_agent: false, }
I would be glad, if you could teach me what I can do to solve this problem.
I have already added a public key on the bitbucket, but it doesn't work.
*
SSH agent forwarding report
[success] repo_url
setting ok
[success] ssh private key file exists
[success] ssh-agent
process seems to be running locally
[success] ssh-agent
process recognized by ssh-add
command
[success] ssh private keys added to ssh-agent
[success] application repository accessible from local machine
[success] all hosts using passwordless login
[success] forward_agent
ok for all hosts
[success] ssh agent successfully forwarded to remote hosts
[success] application repository accessible from remote hosts
It seems SSH agent forwarding is set up correctly! You can continue
with the deployment process.
It succeeded in all tests, but still makes same error.
See Question&Answers more detail:
os