text 流浪汉-SSH-错误

Posted 2021-05-03

## blt vm
padmin@ClintUbuntu:~/www/sites/***$ blt vm
[error]  Drupal VM config has been initialized, but the VM has not been created. Please re-run `blt vm`. 
/home/padmin/www/sites/***/blt/project.local.yml was modified.
BLT will now use @***.local as the default drush alias for all commands on this machine.
 Do you want to boot Drupal VM? (y/n) y
In future, run vagrant up to boot the VM.
[Exec] Running vagrant up in /home/padmin/www/sites/***
Bringing machine '***' up with 'virtualbox' provider...
==> ***: Preparing master VM for linked clones...
    ***: This is a one time operation. Once the master VM is prepared,
    ***: it will be used as a base for linked clones, making the creation
    ***: of new VMs take milliseconds on a modern system.
==> ***: Importing base box 'geerlingguy/ubuntu1604'...
==> ***: Cloning VM...
==> ***: Matching MAC address for NAT networking...
==> ***: Checking if box 'geerlingguy/ubuntu1604' is up to date...
==> ***: Setting the name of the VM: local.***.com
==> ***: Clearing any previously set network interfaces...
==> ***: Preparing network interfaces based on configuration...
    ***: Adapter 1: nat
    ***: Adapter 2: hostonly
==> ***: Forwarding ports...
    ***: 22 (guest) => 2222 (host) (adapter 1)
==> ***: Running 'pre-boot' VM customizations...
==> ***: Booting VM...
==> ***: Waiting for machine to boot. This may take a few minutes...
    ***: SSH address: 127.0.0.1:2222
    ***: SSH username: vagrant
    ***: SSH auth method: private key
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.
[Exec]  Exit code 1  Time 05:17
[error]  Drupal VM failed to boot. Read Drupal VM's previous output for more information. 
 Do you want to try to re-provision the VM? Sometimes this works. (y/n) y
[Exec] Running vagrant provision in /home/padmin/www/sites/***
==> ***: [vagrant-hostsupdater] Checking for host entries
==> ***: [vagrant-hostsupdater]   found entry for: 192.168.25.8 local.***.com
==> ***: [vagrant-hostsupdater] Writing the following entries to (/etc/hosts)
==> ***: [vagrant-hostsupdater]   192.168.25.8  www.local.***.com  # VAGRANT: 35b7534f754ba53445c0ede787b477f6 (***) / 14c71b7d-e520-40da-8393-6b570fc39485
==> ***: [vagrant-hostsupdater]   192.168.25.8  adminer.local.***.com  # VAGRANT: 35b7534f754ba53445c0ede787b477f6 (***) / 14c71b7d-e520-40da-8393-6b570fc39485
==> ***: [vagrant-hostsupdater]   192.168.25.8  xhprof.local.***.com  # VAGRANT: 35b7534f754ba53445c0ede787b477f6 (***) / 14c71b7d-e520-40da-8393-6b570fc39485
==> ***: [vagrant-hostsupdater]   192.168.25.8  pimpmylog.local.***.com  # VAGRANT: 35b7534f754ba53445c0ede787b477f6 (***) / 14c71b7d-e520-40da-8393-6b570fc39485
==> ***: [vagrant-hostsupdater]   192.168.25.8  dashboard.local.***.com  # VAGRANT: 35b7534f754ba53445c0ede787b477f6 (***) / 14c71b7d-e520-40da-8393-6b570fc39485
==> ***: [vagrant-hostsupdater] This operation requires administrative access. You may skip it by manually adding equivalent entries to the hosts file.
[sudo] password for padmin: 
==> ***: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.3.1.0).

Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode

    ***: Running ansible-playbook...

PLAY [all] *********************************************************************

TASK [Gathering Facts] *********************************************************
fatal: [***]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Connection timed out during banner exchange\r\n", "unreachable": true}
	to retry, use: --limit @/home/padmin/www/sites/***/vendor/geerlingguy/drupal-vm/provisioning/playbook.retry

PLAY RECAP *********************************************************************
***                    : ok=0    changed=0    unreachable=1    failed=0   

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
[Exec]  Exit code 1  Time 41.175s
[error]  Unable to provision virtual machine. This is likely due to an issue with your Drupal VM configuration and not BLT itself. 
padmin@ClintUbuntu:~/www/sites/***$ 


## Vagrant up
padmin@ClintUbuntu:$ vagrant up
Bringing machine '***' up with 'virtualbox' provider...
==> ***: Checking if box 'geerlingguy/ubuntu1604' is up to date...
==> ***: Clearing any previously set forwarded ports...
==> ***: Clearing any previously set network interfaces...
==> ***: Preparing network interfaces based on configuration...
    ***: Adapter 1: nat
    ***: Adapter 2: hostonly
==> ***: Forwarding ports...
    ***: 22 (guest) => 2222 (host) (adapter 1)
==> ***: Running 'pre-boot' VM customizations...
==> ***: Booting VM...
==> ***: Waiting for machine to boot. This may take a few minutes...
    ***: SSH address: 127.0.0.1:2222
    ***: SSH username: vagrant
    ***: SSH auth method: private key
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.