If you are using cap 1.4.1, you really, really, really ought to upgrade to cap 1.4.2. Otherwise, if you also happen to have cap 2.3 (or later) installed, cap 1.4.1 will try to use the wrong net-ssh version. cap 1.4.2 just makes its dependencies smarter, so it always tries to use net-ssh 1.x, instead of 2.x, which will not work with cap 1.x.

- Jamis

On Aug 17, 2008, at 11:26 PM, No BS wrote:


I'm having the exact same problem. Actually, mine was working fine to
begin with. Then I went to "capify" another app and set it up and
accidentally overwrote the ssh key, so I had to go in and re-paste the
public key for the first app, etc. Now I'm getting the error described
above when I try any "cap" command on the first app, even though I can
manually ssh into the server just fine. Has anyone figured this out or
have any idea what's going on?

On Aug 7, 10:17 pm, Bharat <[EMAIL PROTECTED]> wrote:
Hello,
This is driving me crazy, please help.  I have inherited a Ruby on
Rails app that uses Capistrano 1.4.1 and deprec 1.9.2 .  I am on
Ubuntu 7.10.  I have set up ssh public key authentication so that I
can ssh into the machine that I am trying to deploy into.  The
gentleman who was the owner of this app. before me had written an
elaborate deploy.rb using Capistrano 1.4.1 and deprec 1.9.2.  He
advised me to put the following in my .caprc file:

[EMAIL PROTECTED]:~$ cat .caprc
require 'deprec/recipes'
ssh_options[:keys]=%w(/home/bruparel/.ssh/id_rsa)
ssh_options[:paranoid]=false
ssh_options[:forward_agent]=true
[EMAIL PROTECTED]:~$

when I try to run the cap deploy task, I get the following problem:

[EMAIL PROTECTED]:~/work/isabontMain$ RAILS_ENV=staging cap deploy
 * executing task deploy
 * executing task update
** transaction: start
 * executing task before_update_code
 * executing "sudo  date"
   servers: ["staging.isabont.com"]
Password:
*** [before_update_code] transaction: rollback
 * [before_update_code] rolling back
authentication failed for `auth_methodspasswordkeyboard-
interactiveport22usernamedeploypassword **********paranoidfalseforward_agenttruekeys/
home/bruparel/.ssh/id_rsa'
[EMAIL PROTECTED]:~/work/isabontMain$

The only channge that I have made in the above line is substuted a
string of ******** for the password.  Apparently, Capistrano + deprec
is munging the whole thing as a huge string without treating it as a
hash!  How can that happen?

Your help and/or guidance will be most appreciated.

Thanks.

Bharat Ruparel
p.s.  Please note that I am posting this on deprec google group as
well hoping that someone can spot the problem.

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


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to