Thanks for reply. It appeared that the culprit is a SSH proxy command from .ssh/config that uses `nc` to get to nodes in local network through a gateway machine:
Host node.localnet ProxyCommand ssh gateway.example.com exec nc %h %p Is it really necessary to use `nc` for this scenario? What is the common way to do this in Capistrano? On Tuesday, March 13, 2012 10:06:39 PM UTC+3, Lee Hambley wrote: > > Anatoly, > > This isn't normal, and must be a misconfiguration, or failed exit from > Cap, I would kill those connections, and see if they come back. Also > consider investing time in hiring someone who is experienced with server > security, to make sure you haven't been breached, and it isn't someone > having compromised your `deploy` user. > > - Lee > > On 13 March 2012 15:47, anatoly techtonik <[email protected]> wrote: > >> Hi, >> >> I am new to Capistrano, and the script I use is not written by me. >> Is it ok for Capistrano to leave open SSH connections without TTY for >> several weeks? >> >> I observe about 20 open connections on deployment server. All from >> different users, who >> are not connected and have not used the server for a long time, except >> through >> automatic Capistrano deployment script. >> >> I suspect that Capistrano may leave them open in case of error during >> deployment. >> Can anybody confirm this? If that is the case - is it a bug or these >> sessions are useful >> for something (troubleshooting)? >> >> Thanks for answers. Hopefully, I didn't interrupt your beer drinking >> process. ;) >> -- >> anatoly t. >> >> -- * 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.com/group/capistrano?hl=en
