GithubHelp home page GithubHelp logo

Comments (6)

leehambley avatar leehambley commented on September 27, 2024

from sshkit.

thbar avatar thbar commented on September 27, 2024

I just tried (with commit 692a5f4) but the error is still happening:

$ bundle exec cap vagrant deploy
warning: thread "Ruby-0-Thread-2: /Users/thbar/.rbenv/versions/jruby-9.2.13.0/lib/ruby/gems/shared/bundler/gems/sshkit-692a5f4fc190/lib/sshkit/runners/parallel.rb:10" terminated with exception (report_on_exception is true):
SSHKit::Runner::ExecuteError: Exception while executing as [email protected]: connection closed by remote host
  execute at /Users/thbar/.rbenv/versions/jruby-9.2.13.0/lib/ruby/gems/shared/bundler/gems/sshkit-692a5f4fc190/lib/sshkit/runners/parallel.rb:15
(Backtrace restricted to imported tasks)
cap aborted!
SSHKit::Runner::ExecuteError: Exception while executing as [email protected]: connection closed by remote host

from sshkit.

leehambley avatar leehambley commented on September 27, 2024

Since you are deploying to vagrant machine locally, one assumes, maybe there's an actual connection problem?

Is "vagrant" using IP addresses or hostnames, are you on a VPN, is your machine definitely up, and already accepting SSH connections?

from sshkit.

thbar avatar thbar commented on September 27, 2024

My obfuscation made things less clear - I actually made 2 different attempts:

  • The first one to production, connects via a VPN to a Ubuntu machine, by using its IP, to a machine which was up (I switched to MRI right after, and managed to deploy successfully)
  • The second one is to a vagrant VM (VirtualBox), which is accepting SSH connections

I'll make further investigation (including upgrading JRuby just in case), and will share my findings here.

from sshkit.

thbar avatar thbar commented on September 27, 2024

I am also seeing this problem on another use-case apparently (unrelated to capistrano, but using net/sftp to target an even different server). Investigating, will report back.

from sshkit.

thbar avatar thbar commented on September 27, 2024

@leehambley after investigating, it turns out this is not caused by sshkit but instead is a problem due to an upgrade of net/ssh from 5.2.0 to 6.1.0.

It is probably a mis-configuration or other client-specific trouble.

I'll close the current ticket, sorry for the noise & thanks for your replies!

from sshkit.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.