You don't provide a lot of details about what specifically is failing. However I have run into two issues in the past which had me stumped for a bit.
1) If cap is reaching out to another server (e.g. to pull down a github repo accessible via keypairs) this was needed in order that the second connect passes along your keys as well: # easy deploy from github # see : http://blog.theedgecase.com/2008/7/15/easier-capistrano-deployments-from-github set :ssh_options, {:forward_agent => true} 2) Issues with ssh on the remote host failing (silently) because of the failure of the second ssh connection (again e.g. github pull of repo via ssh) due to known_hosts issues. I resolved this by putting the following in USERDIR/.ssh/config Host * StrictHostKeyChecking no UserKnownHostsFile=/dev/null This causes the remote ssh host to never check for hosts in the known hosts file and causes it to ignore any existing known hosts file. Hope that helps you (or someone else). G On Aug 11, 7:11 am, Elijah Wright <[email protected]> wrote: > Hi there, > > I'm having some difficulty tracking down the cause of a bit of nuisance > behavior when trying to automate some deploys. > > Basically, what I'm doing is having our svn repository's post-commit hook > fire off a background deploy. Let's ignore the mechanism for that for now - > I've rigged this up in several different ways, and in every case have hit > the same issue. > > Under normal circumstances, our developers all have SSH keys, and deploys > are passwordless (other than the passphrases used to unlock the local dev's > key - many use ssh-agent or something similar). > > But when I fire off a deploy in any other fashion than with a "real" login > session fronting it, things seem to go completely off the rails (sorry, > joke...). Cap starts prompting for passwords for things that we have been > using keys to control for *ages*. > > Is there a community collection of tips for debugging oddball SSH and keying > issues? I'm pretty much stumped by this behavior. > > Is there an environment variable that really *must* be set to get ssh keys > to work properly, but that my scripted deploy might not have set? > > Again - I'll re-iterate - when I deploy from the command line, everything > works perfectly. > > thanks in advance, > > --elijah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Capistrano" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
