

先ほどまでずっと **vagrant ssh**
の状態でsassを使い遊んでいて、新しいタブで効率よくしようと思い2個ほど新しくターミナルを開いたらていつものように **vagrant up** をしたら

[code]

    > 
    ==> 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 few 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 unable to communicate with the guest machine within
    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 usually good hints as to what may be wrong.
    >
    If you're using a custom box, make sure that networking is properly
    working and you're able to connect to the machine. It is a common
    problem that networking isn't setup properly in these boxes.
    Verify that authentication configurations are also setup properly,
    as well.
    >
    If the box appears to be booting properly, you may want to increase
    the timeout ("config.vm.boot_timeout") value.
    
[/code]

こんなエラーが出ました。当然 **vagrant ssh** もできずにエラーが出ます

[code]

    ssh_exchange_identification: Connection closed by remote host
    
[/code]

後、気になった症状といえばsassで何十回か変換した後に何も動かなくなったことです。順番的に言えば急に動かなくなったと同時に新しいタブを開きました。  
ドットインストールを参考に導入しました。  
ゲストからの質問で恐縮ですが、何卒よろしくお願いします。


CC BY-SA 3.0
2015-08-15T12:55:11.860
14445
2015-08-17T02:46:13.040
2015-08-16T10:38:58.023
5519
10935
question
macos vagrant
急にVagrant upができなくなった


似たような症状になったことがあります。

私の環境では一度 `vagrant halt` で仮想環境を落とし、その後`vagrant up` すると正常起動しましたので一度試してみてください。


CC BY-SA 3.0
2015-08-17T02:46:13.040
14505
2015-08-17T02:46:13.040
3271
14445
answer