gistfile1.txt

nels.nelson@sol:~/src/abacus-fork[inframon-34]$ vagrant up
Bringing machine 'abacus' up with 'virtualbox' provider...
Bringing machine 'abacus_build' up with 'virtualbox' provider...
[abacus] Importing base box 'centos-6.5-64-vagrant'...
[abacus] Matching MAC address for NAT networking...
[abacus] Clearing any previously set forwarded ports...
[abacus] Creating shared folders metadata...
[abacus] Clearing any previously set network interfaces...
[abacus] Preparing network interfaces based on configuration...
[abacus] Forwarding ports...
[abacus] -- 22 => 2222 (adapter 1)
[abacus] -- 80 => 8000 (adapter 1)
[abacus] -- 5000 => 5000 (adapter 1)
[abacus] Running 'pre-boot' VM customizations...
[abacus] Booting VM...
[abacus] Waiting for machine to boot. This may take a few minutes...
[abacus] Machine booted and ready!
[abacus] Mounting shared folders...
[abacus] -- /vagrant
[abacus] -- /tmp/vagrant-puppet/manifests
[abacus_build] Importing base box 'centos-6.5-64-vagrant'...
[abacus_build] Matching MAC address for NAT networking...
[abacus_build] Clearing any previously set forwarded ports...
[abacus_build] Fixed port collision for 22 => 2222. Now on port 2200.
Vagrant cannot forward the specified ports on this VM, since they
would collide with some other application that is already listening
on these ports. The forwarded port to 8000 is already in use
on the host machine.

To fix this, modify your current projects Vagrantfile to use another
port. Example, where '1234' would be replaced by a unique host port:

  config.vm.network :forwarded_port, guest: 80, host: 1234

Sometimes, Vagrant will attempt to auto-correct this for you. In this
case, Vagrant was unable to. This is usually because the guest machine
is in a state which doesn't allow modifying port forwarding.
nels.nelson@sol:~/src/abacus-fork[inframon-34]$