Picture of Graham Sandersfield
Installation Time out
by Graham Sandersfield - Wednesday, 14 December 2016, 11:34 AM
 

I am excited about using Adapt Learning but can't get it to install correctly - I get a timeout when looking for the private key.  I am trying to install on a Windows 7 Professional 64bit

I have tried a lot of things but not a developer and so am struggling to figure how to generate a private key and point towards it.  Any help would be appreciated.  Below is the command prompt content

 

 

C:\AdaptLearning>cd adapt_authoring-master

C:\AdaptLearning\adapt_authoring-master>vagrant halt
==> default: Attempting graceful shutdown of VM...
default: Guest communication could not be established! This is usually becau
se
default: SSH is not running, the authentication information was changed,
default: or some other networking issue. Vagrant will force halt, if
default: capable.
==> default: Forcing shutdown of VM...

C:\AdaptLearning\adapt_authoring-master>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty32' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 5000 (guest) => 5000 (host) (adapter 1)
default: 5858 (guest) => 5858 (host) (adapter 1)
default: 27017 (guest) => 27027 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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

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.

C:\AdaptLearning\adapt_authoring-master>