(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,}

我会很高兴,如果你能教我能做什么来解决这个问题.

我已经在bitbucket上添加了一个公钥,但它不起作用.

*

SSH代理转发报告

---

1. [success] repo_url setting ok

2. [success] ssh private key file exists

3. [success] ssh-agent process seems to be running locally

4. [success] ssh-agent process recognized by ssh-add command

5. [success] ssh private keys added to ssh-agent

6. [success] application repository accessible from local machine

7. [success] all hosts using passwordless login

8. [success] forward_agent ok for all hosts

9. [success] ssh agent successfully forwarded to remote hosts

10. [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.