Closed lovethatnixter closed 6 years ago
lcatlett
commented
6 years ago @lovethatnixter after running blt vm and booting the vm with vagrant up, you should be running blt commands from within the guest vm, not your host. Errors like "exports:2: path contains non-directory or non-existent components" are occuring because these paths dont exist as writable directories in the bm.
lovethatnixter
commented
6 years ago Once I get onto the VM the VM doesn't know what BLT is.
Bringing machine 'cu-acsf' up with 'virtualbox' provider...
==> cu-acsf: Checking if box 'geerlingguy/ubuntu1604' is up to date...
==> cu-acsf: [vagrant-hostsupdater] Checking for host entries
==> cu-acsf: [vagrant-hostsupdater] found entry for: 192.168.30.172 local.cu-acsf.com
==> cu-acsf: [vagrant-hostsupdater] found entry for: 192.168.30.172 www.local.cu-acsf.com
==> cu-acsf: [vagrant-hostsupdater] found entry for: 192.168.30.172 dashboard.local.cu-acsf.com
==> cu-acsf: [vagrant-hostsupdater] found entry for: 192.168.30.172 www.dashboard.local.cu-acsf.com
==> cu-acsf: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> cu-acsf: flag to force provisioning. Provisioners marked to run always will still run.
==> cu-acsf: Machine 'cu-acsf' has a post `vagrant up` message. This is a message
==> cu-acsf: from the creator of the Vagrantfile, and not from Vagrant itself:
==> cu-acsf:
==> cu-acsf: Your Drupal VM Vagrant box is ready to use!
==> cu-acsf: * Visit the dashboard for an overview of your site: http://dashboard.local.cu-acsf.com (or http://192.168.30.172)
==> cu-acsf: * You can SSH into your machine with `vagrant ssh`.
==> cu-acsf: * Find out more in the Drupal VM documentation at http://docs.drupalvm.com
DOIT-NJS39772M5:cu-acsf nickstankus$ vagrant ssh
Welcome to Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
vagrant@local:~$ blt setup
No command 'blt' found, did you mean:
Command 'btt' from package 'blktrace' (universe)
Command 'llt' from package 'storebackup' (universe)
Command 'bat' from package 'bacula-console-qt' (universe)
Command 'bat' from package 'bareos-bat' (universe)
Command 'bls' from package 'bacula-sd' (universe)
Command 'bls' from package 'bareos-tools' (universe)
Command 'lt' from package 'looptools' (universe)
Command 'bld' from package 'bld' (universe)
Command 'slt' from package 'slt' (universe)
Command 'lbt' from package 'lbt' (universe)
blt: command not found
vagrant@local:~$ 
pixlkat
commented
6 years ago @lovethatnixter it looks like vagrant is complaining about invalid entries in your exports file on your mac. You might try checking /etc/exports for improper entries. The lines added by vagrant will be surrounded by VAGRANT-BEGIN and VAGRANT-END. You can manually delete anything that is invalid from there and save the file (you'll need to use sudo to do so).
lovethatnixter
commented
6 years ago That got rid of the strange file path.
# VAGRANT-BEGIN: 502 326aacb3-47b4-4957-af88-b508a2c88d36
"/Users/acquia-blt/drupal8_cu_blt" 192.168.156.111 -alldirs -mapall=502:20
# VAGRANT-END: 502 326aacb3-47b4-4957-af88-b508a2c88d36but now the issue seems to be archive.apache.org and solr.
TASK [geerlingguy.solr : Download Solr.] ***************************************
fatal: [cu-blt-acsf]: FAILED! => {"changed": false, "msg": "Failed to connect to archive.apache.org at port 443: [Errno 110] Connection timed out"}
to retry, use: --limit @/vagrant/vendor/geerlingguy/drupal-vm/provisioning/playbook.retry
PLAY RECAP *********************************************************************
cu-blt-acsf : ok=206 changed=0 unreachable=0 failed=1
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
[Exec] Exit code 1 Time 05:06
[error] Unable to provision virtual machine. This is likely due to an issue with your Drupal VM configuration and not BLT itself.
ba66e77
commented
6 years ago @lovethatnixter I've blown away and rebuilt my local VM and have not been able to replicate the issue you're seeing. We occasionally see transient routing issues like this but if it is consistent for you then you might try a traceroute to get a better sense of where the problem lies.
lovethatnixter
commented
6 years ago At this point I think it is fixed. I was able to download at a different location. It seems to be location based.
ba66e77
commented
6 years ago Glad it's all working for you now!
My system information:
Output of
blt doctor:When I run this command:
I get the following output:
And I expected this to happen: