Hello Alvaro,
Thanks for the reply. I've tried doing vagrant init and vagrant up and
vagrant init and it failed with a timeout message. The ruby error is
intermittent, it seems. The timeouts seem to be happening much more often.
However, this time, after running vagrant init and vagrant up, I got the
error on the vagrant destroy:
[wyatt@oc4642434687 ibm-cds-appserver]$ vagrant box list
IBM.EI.RHEL.6 (vmware_desktop, 0)
IBM.EI.RHEL.6 (virtualbox, 6.7.20151128)
opscode-ubuntu-14.04 (vmware_desktop, 0)
[wyatt@oc4642434687 ibm-cds-appserver]$ vagrant init IBM.EI.RHEL.6
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
[wyatt@oc4642434687 ibm-cds-appserver]$ vagrant up
Bringing machine 'default' up with 'vmware_workstation' provider...
==> default: Cloning VMware VM: 'IBM.EI.RHEL.6'. This can take some time...
==> default: Checking if box 'IBM.EI.RHEL.6' is up to date...
==> default: Skipping vmnet device verification, verify_vmnet is set to
false.
==> default: Preparing network adapters...
==> default: Fixed port collision for 22 => 2222. Now on port 2201.
==> default: Starting the VMware VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 192.168.211.147:22
default: SSH username: vagrant
default: 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.
[wyatt@oc4642434687 ibm-cds-appserver]$ vagrant destroy 5e9ff42
default: Are you sure you want to destroy the 'default' VM? [y/N] y
==> default: Stopping the VMware VM...
==> default: Deleting the VM...
ruby: error while loading shared libraries: libruby.so.2.2: cannot open
shared object file: No such file or directory
Not sure what is really going on, but things don't seem to be very stable
right now.
Thanks,
Michael
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/dac9f131-554f-4d24-8174-b56a2c31e526%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
