Suddenly, I can't do Vagrantup.

I've been playing with sass in vagrant ssh, and I opened two new terminals to make them more efficient with a new tab, and I did vagrant up as usual.

> 
==>default: Checking if box'chef/centos-6.5' is up to date...
==>default:Resuming suspended VM...
==>default: Booting VM...
==>default: Waiting for machine to boot. This may take a new minutes...
    default:SSH address:127.0.0.1:2222
    default:SSH username:vagrant
    default:SSH auth method:private key
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
    default:Warning:Connection timeout.Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unavailable to communicate with the guest machine with in
The configured("config.vm.boot_timeout" value) time period.
>
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine.These errors
Are usally good hits as to what may be wrong.
>
If you're using a custom box, make sure that networking is proper
working and you're able to connect to the machine.It is a common
problem that networking isn't setup proper in these boxes.
Verify that authentication configurations are also setup proper,
as well.
>
If the boxappears to be booting professionally, you may want to increase
The timeout("config.vm.boot_timeout") value.

I got this error.Naturally, vagrant ssh fails and the error occurs

 ssh_exchange_identification:Connection closed by remote host

Also, the symptom that bothered me was that after converting with sass several times, nothing moved.To put it in order, I opened a new tab at the same time as it suddenly stopped working.
I introduced it by referring to dot installation.
I'm sorry for the guest's question, but I appreciate your cooperation.

macos vagrant

2022-09-30 17:57

1 Answers

I have had similar symptoms.

In my environment, I dropped the virtual environment with vagrant half and then vagrant up and it started normally, so please try it.

2022-09-30 17:57

If you have any answers or tips

Popular Tags

python x 4647

android x 1593

java x 1494

javascript x 1427

c x 927

c++ x 878

ruby-on-rails x 696

php x 692

python3 x 685

html x 656