search

ptwobrussell / Mining-the-Social-Web-2nd-Edition

The official online compendium for Mining the Social Web, 2nd Edition (O'Reilly, 2013)
http://bit.ly/135dHfs
Other
2.9k stars 1.49k forks source link

Vagrant up -- running but not connecting #251

Closed nataliabueno closed 9 years ago

nataliabueno commented 9 years ago

Hi all,

I'm using OS X Yosemite 10.10.1. Before upgrading to Yosemite, things were running smoothly with vagrant. Now, after re-installing VB and many other things, I can't seem to get vagrant to work properly. I installed vagrant, but whenever I do "vagrant up", I get the following:

Bringing machine 'default' up with 'virtualbox' provider...

Then, I try going to http://localhost:8888 and I get an error. But, when I try "vagrant status", I get this:

Current machine states:

default running (virtualbox)

The VM is running. To stop this VM, you can run vagrant halt to shut it down forcefully, or you can run vagrant suspend to simply suspend the virtual machine. In either case, to restart it again, simply run vagrant up.

Any help? Thanks!

nataliabueno commented 9 years ago

Oh, and my Virtualbox version is 4.3.18r96516 and my Vagrant version is 1.7.2.

ptwobrussell commented 9 years ago

If memory serves, you will have to reinstall the latest version of virtualbox because some stuff changed on the file system as part of your Yosemite upgrade

---Sent from Boxer | http://getboxer.com

On January 18, 2015 at 6:02:16 PM CST, Natalia Bueno notifications@github.com wrote:Hi all, I'm using OS X Yosemite 10.10.1. Before upgrading to Yosemite, things were running smoothly with vagrant. Now, after re-installing VB and many other things, I can't seem to get vagrant to work properly. I installed vagrant, but whenever I do "vagrant up", I get the following: Bringing machine 'default' up with 'virtualbox' provider... Then, I try going to http://localhost:8888 and I get an error. But, when I try "vagrant status", I get this: Current machine states: default running (virtualbox) The VM is running. To stop this VM, you can run vagrant halt to shut it down forcefully, or you can run vagrant suspend to simply suspend the virtual machine. In either case, to restart it again, simply run vagrant up . Any help? Thanks! —Reply to this email directly or view it on GitHub.

nataliabueno commented 9 years ago

Hi, I had already re-installed it. Thanks for the quick feedback, though. Any other thoughts?

cerealkill commented 9 years ago

Hi, Have you tried running 'sudo netstat -tulpn ' ou 'sudo netstat -tulpn | grep 8888' before running vagrant? Maybe there are port conflicts. Mine versions are 4.3.10_Ubuntur93012 and 1.4.3. They are a little backdated but using latest was giving me lots of random problems. I had to run 'vagrant destroy' and 'vagrant up' multiple times until it finally ran chef succesfully once and got the provisioning done right.

On Mon, Jan 19, 2015 at 12:59 PM, Natalia Bueno notifications@github.com wrote:

Hi, I already re-installed it -- for some reason, it was uninstalled during my upgrade. Thanks for the quick feedback, though. Any other thoughts?

— Reply to this email directly or view it on GitHub https://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition/issues/251#issuecomment-70506236 .

cerealkill commented 9 years ago

Maybe you could try running 'vagrant up --provison' to check if the provisioning is ok.

On Mon, Jan 19, 2015 at 1:45 PM, J. Paul Depraz deprazz@gmail.com wrote:

Hi, Have you tried running 'sudo netstat -tulpn ' ou 'sudo netstat -tulpn | grep 8888' before running vagrant? Maybe there are port conflicts. Mine versions are 4.3.10_Ubuntur93012 and 1.4.3. They are a little backdated but using latest was giving me lots of random problems. I had to run 'vagrant destroy' and 'vagrant up' multiple times until it finally ran chef succesfully once and got the provisioning done right.

On Mon, Jan 19, 2015 at 12:59 PM, Natalia Bueno notifications@github.com wrote:

Hi, I already re-installed it -- for some reason, it was uninstalled during my upgrade. Thanks for the quick feedback, though. Any other thoughts?

— Reply to this email directly or view it on GitHub https://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition/issues/251#issuecomment-70506236 .

nataliabueno commented 9 years ago

Hi Paul, thanks! I ran Vagrant up --provision and it gave me some clues that there were some port conflicts. After some reading some dismal comments about these problems, I decided to try a hammer solution: I uninstalled vagrant and re-installed it -- using a different version. It seems to work. Thanks!

dan-king commented 9 years ago

@nataliabueno, re " I uninstalled vagrant and re-installed it -- using a different version. It seems to work.". That's promising! What version of vagrant is working for you? (I'm having no success with vagrant 1.7.2, the latest version.)

dan-king commented 9 years ago

I finally got it to work by uninstalling vagrant 1.7.2 and installing 1.7.1 instead.

Yosemite 10.10.1 VirtualBox 4.3.20 Vagrant 1.7.1 Created links as described in #243