Capistrano初始部署失败

时间:2012-06-20 20:41:09

标签: ruby-on-rails-3 capistrano vps

将Capistrno的Rails 3项目部署到linode VDS时遇到了麻烦。错误看起来像:

lifecoder@lifecoder-VirtualBox:~/projects/ruby/avtolife$ cap deploy:update
  * executing `deploy:update'
 ** transaction: start
  * executing `deploy:update_code'
    updating the cached checkout on all servers
    executing locally: "git ls-remote git@bitbucket.org:lifecoder/avtolife.git master"
    command finished in 2964ms
  * executing "if [ -d /srv/avtolife/shared/cached-copy ]; then cd /srv/avtolife/shared/cached-copy && git fetch -q origin && git fetch --tags -q origin && git reset -q --hard aec5c7f44151ca74d8eb384c478d6707719ee680 && git clean -q -d -x -f; else git clone -q git@bitbucket.org:lifecoder/avtolife.git /srv/avtolife/shared/cached-copy && cd /srv/avtolife/shared/cached-copy && git checkout -q -b deploy aec5c7f44151ca74d8eb384c478d6707719ee680; fi"
    servers: ["original-parts.net"]
    [lifecoder@original-parts.net] executing command
 ** [original-parts.net :: err] Host key verification failed.
 ** [original-parts.net :: err] fatal: The remote end hung up unexpectedly
    command finished in 1401ms
*** [deploy:update_code] rolling back
  * executing "rm -rf /srv/avtolife/releases/20120620203352; true"
    servers: ["original-parts.net"]
    [lifecoder@original-parts.net] executing command
    command finished in 588ms
    failed: "rvm_path=$HOME/.rvm/ $HOME/.rvm/bin/rvm-shell '1.9.2' -c 'if [ -d /srv/avtolife/shared/cached-copy ]; then cd /srv/avtolife/shared/cached-copy && git fetch -q origin && git fetch --tags -q origin && git reset -q --hard aec5c7f44151ca74d8eb384c478d6707719ee680 && git clean -q -d -x -f; else git clone -q git@bitbucket.org:lifecoder/avtolife.git /srv/avtolife/shared/cached-copy && cd /srv/avtolife/shared/cached-copy && git checkout -q -b deploy aec5c7f44151ca74d8eb384c478d6707719ee680; fi'" on lifecoder@original-parts.net

我需要了解如何跟踪特定错误的执行位置。我是* nix和rails的新手,所以config的某些部分对我来说看起来很神奇:(

1 个答案:

答案 0 :(得分:0)

当Capistrano部署出现问题时 - 在远程服务器上逐个运行方案命令。我的问题在于目标服务器 - 本地Ubuntu要求接受远程IP地址,并在没有来自cap脚本的答案时死亡。接受后,同样的脚本运行良好。

相关问题