As for that unfortunate exception...there isn't any option for asking
for a better stack trace, though there ought to be. You'll probably
need to grep through the code for "connection failed for" and then
determine how to get the stack trace for the exception in question. If
you figure it out, please let me know, since this is definitely
something that cap should handle more gracefully.
- Jamis
On Jun 26, 2008, at 8:08 PM, cnk wrote:
>
> I asked for some help on IRC and was told that cap probably can't use
> ssh-agent forwarded keys. So I tried changing this to use password. So
> my stripped down Capfile now looks like:
>
> set :user, 'cnk'
> set :password, "mypass"
> set :ssh_options, { :port => 2202 }
>
> role :app, "xxx.yyy"
>
> I tried getting a new terminal what did not know anything about ssh-
> agent and my keys and then logging in using a password to get to dev.
> I can ssh from dev -> production using the password in my Capfile. But
> cap can't. I get the same error:
>
> cap invoke COMMAND='uname -a'
> * executing `invoke'
> * executing "uname -a"
> servers: ["xxx.yyy"]
> connection failed for: xxx.yyy (NoMethodError: private method `split'
> called for nil:NilClass)
>