failed ssh

827 views
Skip to first unread message

Umarzuki Mochlis

unread,
Sep 9, 2018, 6:11:12 AM9/9/18
to Vagrant
vagrant.exe -v
Vagrant 2.1.4

OS: Windows 10

I failed vagrant ssh with below errors, how do I fix it?

C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/util/subprocess.rb:158:in `rescue in execute':  (216) (Vagrant::Util::Subprocess::LaunchError)
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/util/subprocess.rb:151:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/util/subprocess.rb:22:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/util/ssh.rb:99:in `exec'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/action/builtin/ssh_exec.rb:39:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/plugins/providers/virtualbox/action/check_running.rb:16:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/plugins/providers/virtualbox/action/check_created.rb:16:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/machine.rb:239:in `action_raw'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/machine.rb:208:in `block in action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/machine.rb:190:in `block in action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/machine.rb:194:in `action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/plugins/commands/ssh/command.rb:66:in `block in execute'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/plugin/v2/command.rb:238:in `block in with_target_vms'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/plugin/v2/command.rb:232:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/plugin/v2/command.rb:232:in `with_target_vms'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/plugins/commands/ssh/command.rb:46:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/cli.rb:54:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/lib/vagrant/environment.rb:294:in `cli'
        from C:/HashiCorp/Vagrant/embedded/gems/2.1.4/gems/vagrant-2.1.4/bin/vagrant:164:in `<main>'

Umarzuki Mochlis

unread,
Sep 9, 2018, 8:24:03 AM9/9/18
to Vagrant
solved using git bash instead of mobaxterm

myk

unread,
Feb 2, 2020, 8:21:18 AM2/2/20
to Vagrant
If Googling ever drops somebody here. A trick you can use is to first run cmd.exe from MobaXterm and then run vagrant !
Reply all
Reply to author
Forward
0 new messages