My mistake, it's the ssh connection which is failing. We also modified the port that SSH is listening on.
I added ssh_options[:port] = <new port> to my recipe, but it appears that the SSH connection isn't working. It hangs on the first "executing command" message. I should mention that the target machine for both "web" and "app" roles is actually a different IP than the one being used to make the SSH call. Meaning that I am SSHing to IP x.y.z.w port P but really am being routed to IP a.b.c.d port 22. Sadly, I do not have enough networking knowledge to describe that with the right term (is it port forwarding?). However, I can successfully ssh to that host using the hostname / port combination with Putty (a client side app.), which I would assume should allow cap/netSSH to see the host using the same setup? How can I further debug this? Thanks, Wes Wes Gamble wrote: > All, > > I'm using cap 1.4.1 against CVS. We just modified the CVS server to run > pserver on a non-default port, so I modified my :repository string in my > deploy recipe to: > > set :repository, ":pserver:userid:[EMAIL PROTECTED]:port/path/to/cvs" > > :scm is set to "cvs" > > and my cap script appears to hang trying to talk to the CVS server. Is > there something else I need to do in order to allow cap to see the CVS > server on the new port? > > Thanks, > Wes > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
