Unable to install and download vagrant

[reenamadamwar]

I followed https://github.com/vlead/setup-ovpl-centos/blob/develop/user-docs/run-ads-using-vagrant-box.org this document but unable to download and install vagrant box.

[sivashankerN]

Deleted the text

[sivashankerN]

Good morning Shiva I downloaded and install virtualbox 5.1 then i did apt-get install linux-headers-generic apt-get install linux-image-generic then I reboot the machine uname -r uname -a /sbin/vboxconfig same timed out error is coming

[reenamadamwar]

I followed this document and installed VirtualBox 5.2 and Vagrant 2.0.1

But when I run vagrant up, I get a timeout error:

Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'ads-on-centos'... ==> default: Matching MAC address for NAT networking... ==> default: Setting the name of the VM: ads-on-centos_default_1515483550170_27117 ==> default: Fixed port collision for 22 => 2222. Now on port 2200. ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: Forwarding ports... default: 22 (guest) => 2200 (host) (adapter 1) ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2200 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.

Can someone please help me on this.

[sivashankerN]

@reenamadamwar

1. Destroy the vagrant box that you have created. vagrant destroy
2. Uninstall VirtualBox 5.2 version
3. Install VirtualBox 5.1 version
4. and follow the steps mentioned in the document.

[reenamadamwar]

I searched this issue on google and got this issue and I found that by adding vb.customize ["modifyvm", :id, "--cableconnected1", "on"] this in vagrantfile it should work.

Now after running vagrant up, I get following result :

vagrant up /home/vlab/ads-on-centos/Vagrantfile:36:in block in <top (required)>': undefined local variable or methodvb' for main:Object (NameError) from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/config/v2/loader.rb:37:in load' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/config/loader.rb:125:inblock (2 levels) in load' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/config/loader.rb:119:in each' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/config/loader.rb:119:inblock in load' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/config/loader.rb:116:in each' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/config/loader.rb:116:inload' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:28:in initialize' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:810:innew' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:810:in vagrantfile' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:556:inhost' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:214:in block in action_runner' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/runner.rb:33:inrun' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:543:in hook' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:792:inunload' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/bin/vagrant:141:in ensure in <main>' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/bin/vagrant:141:in

' vlab@coep:~/ads-on-centos$

What it means can somebody tell me?

[sivashankerN]

@reenamadamwar

1. Destroy the vagrant box that you have created. vagrant destroy
2. Uninstall VirtualBox 5.2 version
3. Install VirtualBox 5.1 version
4. and follow the steps mentioned in the document.

[sivashankerN]

To destroy the vagrant box that you have created Go to the directory where you have run "vagrant up". There you can see Vagrantfile in that directory. Then execute the below command vagrant destroy

[reenamadamwar]

after vagrant destroy got this result default: VM not created. Moving on...

And still I am able to see ads-on-centos box in vagrant box list

[reenamadamwar]

able to destroy with the help of this command vagrant box remove -f ads-on-centos

[sivashankerN]

Fine then. now, follow the steps mentioned in the document except downloading ads box( wget command).

[reenamadamwar]

1. Destroyed vagrant box which was downloaded.
2. Un-installed VirtualBox 5.2 version and installed VirtualBox 5.1 version from link as suggested.
3. Followed the steps as given in the document. But in step 7 i.e. on vagrant up command, getting timed out error

Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'ads-on-centos'... ==> default: Matching MAC address for NAT networking... ==> default: Setting the name of the VM: ads-on-centos_default_1515493646086_98964 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: Forwarding ports... default: 22 (guest) => 2222 (host) (adapter 1) ==> 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.

[reenamadamwar]

@sivashankerN As you suggested, I have installed teamviewer. You can connect to my machine now.

[sivashankerN]

@reenamadamwar

maybe the problem with ads box that you downloaded.

Can you try creating one box ( not ads box) with any os? and try doing "vagrant up"

Please google it for how to run vagrant boxes

Please follow the steps mentioned at http://www.vagrantbox.es/ $ vagrant box add {title} {url} $ vagrant init {title} $ vagrant up

[reenamadamwar]

@sivashankerN Yes the problem was with ads box. So I downloaded envimation/ubuntu-xenial box from http://www.vagrantbox.es/ and it works

@ksripathi Please confirm OS version that support analytics-dashboard service

[reenamadamwar]

@ksripathi

While following document to run ADS service, in step 18 after giving lab id and lab sources url in http://local-ads.com:8080. It is throwing error shown in below image

And in log files getting some object has no attribute "output" error