After downloading the file m034.zip, but after runnig “vagrant up ldap”, the following message is returned
Bringing machine ‘ldap’ up with ‘virtualbox’ provider…
==> ldap: Importing base box ‘CentoOS 6.4’…
==> ldap: Matching MAC address for NAT networking…
==> ldap: Setting the name of the VM: ldap-server
==> ldap: Clearing any previously set forwarded ports…
==> ldap: Clearing any previously set network interfaces…
==> ldap: Preparing network interfaces based on configuration…
ldap: Adapter 1: nat
ldap: Adapter 2: hostonly
==> ldap: Forwarding ports…
ldap: 22 (guest) => 2222 (host) (adapter 1)
==> ldap: Running ‘pre-boot’ VM customizations…
==> ldap: Booting VM…
==> ldap: Waiting for machine to boot. This may take a few minutes…
ldap: SSH address: 127.0.0.1:2222
ldap: SSH username: vagrant
ldap: SSH auth method: private key
The guest machine entered an invalid state while waiting for it
to boot. Valid states are ‘starting, running’. The machine is in the
‘unknown’ state. Please verify everything is configured
properly and try again.
If the provider you’re using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you’re using VirtualBox, run
vagrant up while the
VirtualBox GUI is open.
The primary issue for this error is thet the provider you’re using is not properly configured, This is very rerely a Vagrant issue.
or this message error:
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,
If the box appears to be booting properly, you may want to increase
the timeout (“config.vm.boot_timeout”) value.
virtualbox 6.0.14 r133895
Virtualization in the BIOS is Enabled
I have successfully started others virtual server like “m103”, “database” etc.
I have the same problem in another pc with Windows 10.
Maybe the file m034.zip is corrupt?
If I can’t use the ldap server, I can’t go on in the m310 course
Can you help me please?