One of the things that changed in 2.5.4 was that the User option in
.ssh/config was finally honored correctly; there may have been a bug
introduced as part of that "fix", but authentication works fine for me
with 2.5.4.

Could you try adding the following option to your deploy.rb:

  ssh_options[:verbose] = :debug

Then run against both 2.5.3 and 2.5.4, redirecting the output to a
different file for each. If you would then email me (jamis at 37signals
d com) those files (after sanitizing any sensitive data from the files,
like user names, host names, passwords, etc.), I could take a look at
them and see if anything suspicious jumps out at me.

- Jamis

On 2/9/09 10:36 PM, Erazor wrote:
> Hello, I have a setup where cap 2.5.3 works perfectly for a long time
> now, but 2.5.4 fails to run.
> 
> First, the interesting part of my deploy.rb:
> 
> set :application, 'mct'
> set :repository, 'svn+ssh://bbzws162/var/svn/rails-mct/trunk'
> set(:deploy_to) { "/var/www/applications/#{application}" }
> set :user, 'rails'
> set :scm, :subversion
> set :deploy_via, :export
> set :runner, 'root'
> default_run_options[:pty] = true
> role :web, 'bbzlin14', :primary => true
> role :app, 'bbzlin14', :primary => true
> role :db, 'bbzlin14', :primary => true
> ssh_options[:keys] = "#{ENV['HOME']}/.ssh/id_dsa"
> 
> Executed with 2.5.3 this works:
> 
>     * executing deploy'
>     * executing deploy:update' ** transaction: start
>     * executing deploy:update_code' executing locally: "svn info svn
> +ssh://bbzws162/var/svn/rails-mct/trunk -rHEAD"
>     * executing "svn export -q -r372 svn+ssh://bbzws162/var/svn/rails-
> mct/trunk /var/www/applications/mct/releases/20090209062621 && (echo
> 372 > /var/www/applications/mct/releases/20090209062621/REVISION)"
> servers: ["bbzlin14"] [bbzlin14] executing command command finished
> 
> But with 2.5.4 it fails:
> 
>     * executing deploy'
>     * executing deploy:update' ** transaction: start
>     * executing deploy:update_code' executing locally: "svn info svn
> +ssh://bbzws162/var/svn/rails-mct/trunk -rHEAD"
>     * executing "svn export -q -r373 svn+ssh://bbzws162/var/svn/rails-
> mct/trunk /var/www/applications/mct/releases/20090209063436 && (echo
> 373 > /var/www/applications/mct/releases/20090209063436/REVISION)"
> servers: ["bbzlin14"] *** [deploy:update_code] rolling back
>     * executing "rm -rf /var/www/applications/mct/releases/
> 20090209063436; true" servers: ["bbzlin14"] ** [deploy:update_code]
> exception while rolling back: Capistrano::ConnectionError, connection
> failed for: bbzlin14 (Net::SSH::AuthenticationFailed: rails)
> connection failed for: bbzlin14 (Net::SSH::AuthenticationFailed:
> rails)
> 
> Tell me what i need to provide for further help in resolving this.
> 
> > 


--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to