Hi,
It is frustrated that I could not get rid of infinite loop of SSH halt.
Go through all the methods of other thread without luck.
Could anyone help?
require 'vagrant-aws'
Vagrant.configure('2') do |config|
config.vm.box = 'dummy'
config.vm.provider 'aws' do |aws, override|
aws.access_key_id = "xxxx"
aws.secret_access_key = "xxxx"
aws.keypair_name = 'ssh-keypair-name'
aws.instance_type = "t2.micro"
aws.region = 'us-east-1'
aws.ami = 'ami-4ae27e22'
override.ssh.username = 'ubuntu'
override.ssh.private_key_path = 'C:\Install\dev\DevOps\ssh-keypair-name.pem'
end
end
Net::SSH::ConnectionTimeout>
DEBUG ssh: Checking whether SSH is ready...
INFO machine: Calling action: read_ssh_info on provider AWS (i-018e25be4fe858e3e)
INFO interface: Machine: action ["read_ssh_info", "start", {:target=>:default}]
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 2 hooks defined.
INFO runner: Running action: machine_action_read_ssh_info #
INFO warden: Calling IN action: #
INFO warden: Calling IN action: #
INFO connect_aws: Connecting to AWS...
INFO warden: Calling IN action: #
INFO warden: Calling OUT action: #
INFO warden: Calling OUT action: #
INFO warden: Calling OUT action: #
INFO interface: Machine: action ["read_ssh_info", "end", {:target=>:default}]
INFO ssh: Attempting SSH connection...
INFO ssh: Attempting to connect to SSH...
INFO ssh: - Host: ec2-54-163-149-53.compute-1.amazonaws.com
INFO ssh: - Port: 22
INFO ssh: - Username: ubuntu
INFO ssh: - Password? false
INFO ssh: - Key Path: ["C:/Install/dev/DevOps/ssh-keypair-name.pem"]
DEBUG ssh: - connect_opts: {:auth_methods=>["none", "hostbased", "publickey"], :config=>false, :forward_agent=>false, :send_env=>false, :keys_only=>true, :verify_host_key=>false, :password=>nil, :port=>22, :timeout=>15, :user_known_hosts_file=>[], :verbose=>:debug, :encryption=>["aes128-cbc", "3des-cbc", "blowfish-cbc", "cast128-cbc", "aes192-cbc", "aes256-cbc", "rijndael-cbc@lysator.liu.se", "idea-cbc", "arcfour128", "arcfour256", "arcfour", "aes128-ctr", "aes192-ctr", "aes256-ctr", "cast128-ctr", "blowfish-ctr", "3des-ctr", "none"], :logger=>#<Logger:0x0000000006fd2608 @level=0, @progname=nil, @default_formatter=#<Logger::Formatter:0x0000000006fd25b8 @datetime_format=nil>, @formatter=nil, @logdev=#<Logger::LogDevice:0x0000000006fd2568 @shift_period_suffix=nil, @shift_size=nil, @shift_age=nil, @filename=nil, @dev=#, @mon_owner=nil, @mon_count=0, @mon_mutex=#>>, :keys=>["C:/Install/dev/DevOps/ssh-keypair-name.pem"]}
DEBUG ssh: == Net-SSH connection debug-level log START ==
DEBUG ssh: D, [2018-07-18T01:17:56.003683 #16240] DEBUG -- net.ssh.transport.session[37e83a0]: establishing connection to ec2-54-163-149-53.compute-1.amazonaws.com:22
DEBUG ssh: == Net-SSH connection debug-level log END ==
INFO ssh: SSH not up: #<Vagrant::Errors::NetSSHException: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.
If the problem persists, please report a bug to the net-ssh project.
Hi, It is frustrated that I could not get rid of infinite loop of SSH halt. Go through all the methods of other thread without luck. Could anyone help?
require 'vagrant-aws' Vagrant.configure('2') do |config| config.vm.box = 'dummy' config.vm.provider 'aws' do |aws, override| aws.access_key_id = "xxxx" aws.secret_access_key = "xxxx" aws.keypair_name = 'ssh-keypair-name' aws.instance_type = "t2.micro" aws.region = 'us-east-1' aws.ami = 'ami-4ae27e22' override.ssh.username = 'ubuntu' override.ssh.private_key_path = 'C:\Install\dev\DevOps\ssh-keypair-name.pem' end end
Net::SSH::ConnectionTimeout> DEBUG ssh: Checking whether SSH is ready... INFO machine: Calling action: read_ssh_info on provider AWS (i-018e25be4fe858e3e) INFO interface: Machine: action ["read_ssh_info", "start", {:target=>:default}] INFO runner: Preparing hooks for middleware sequence... INFO runner: 2 hooks defined. INFO runner: Running action: machine_action_read_ssh_info #
INFO warden: Calling IN action: #
INFO warden: Calling IN action: #
INFO connect_aws: Connecting to AWS...
INFO warden: Calling IN action: #
INFO warden: Calling OUT action: #
INFO warden: Calling OUT action: #
INFO warden: Calling OUT action: #
INFO interface: Machine: action ["read_ssh_info", "end", {:target=>:default}]
INFO ssh: Attempting SSH connection...
INFO ssh: Attempting to connect to SSH...
INFO ssh: - Host: ec2-54-163-149-53.compute-1.amazonaws.com
INFO ssh: - Port: 22
INFO ssh: - Username: ubuntu
INFO ssh: - Password? false
INFO ssh: - Key Path: ["C:/Install/dev/DevOps/ssh-keypair-name.pem"]
DEBUG ssh: - connect_opts: {:auth_methods=>["none", "hostbased", "publickey"], :config=>false, :forward_agent=>false, :send_env=>false, :keys_only=>true, :verify_host_key=>false, :password=>nil, :port=>22, :timeout=>15, :user_known_hosts_file=>[], :verbose=>:debug, :encryption=>["aes128-cbc", "3des-cbc", "blowfish-cbc", "cast128-cbc", "aes192-cbc", "aes256-cbc", "rijndael-cbc@lysator.liu.se", "idea-cbc", "arcfour128", "arcfour256", "arcfour", "aes128-ctr", "aes192-ctr", "aes256-ctr", "cast128-ctr", "blowfish-ctr", "3des-ctr", "none"], :logger=>#<Logger:0x0000000006fd2608 @level=0, @progname=nil, @default_formatter=#<Logger::Formatter:0x0000000006fd25b8 @datetime_format=nil>, @formatter=nil, @logdev=#<Logger::LogDevice:0x0000000006fd2568 @shift_period_suffix=nil, @shift_size=nil, @shift_age=nil, @filename=nil, @dev=#, @mon_owner=nil, @mon_count=0, @mon_mutex=#>>, :keys=>["C:/Install/dev/DevOps/ssh-keypair-name.pem"]}
DEBUG ssh: == Net-SSH connection debug-level log START ==
DEBUG ssh: D, [2018-07-18T01:17:56.003683 #16240] DEBUG -- net.ssh.transport.session[37e83a0]: establishing connection to ec2-54-163-149-53.compute-1.amazonaws.com:22
DEBUG ssh: == Net-SSH connection debug-level log END == INFO ssh: SSH not up: #<Vagrant::Errors::NetSSHException: An error occurred in the underlying SSH library that Vagrant uses. The error message is shown below. In many cases, errors from this library are caused by ssh-agent issues. Try disabling your SSH agent or removing some keys and try again.
If the problem persists, please report a bug to the net-ssh project.