More information. I added ssh_options[:verbose] = :debug to my cap script, and it looks like the authentication is working, but then the SSH client keeps sending packets like this:
[DEBUG] Fri Oct 05 10:32:08 -0500 2007 -- transport.session: sending message >>"\002\000\000\000\004ping"<< and never gets a response. What are these? In fact, regardless of whether I use the known internal IP and port 22 or the new masqueraded IP and special forwarded port whatever, I get this message. I bounced my sshd on the server and I still see this. I recently updated my net-ssh to 1.1.2 - perhaps that is my problem? Thanks, Wes Wes Gamble wrote: > 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 > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
