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

Chef never successfully completed! #159

Closed bigdavejonnyt closed 10 years ago

bigdavejonnyt commented 10 years ago

Its exclamation mark, not mine ; }

Cloned the files from this repository and ran 

vagrant up

Installed the instance but chef borked before the end. Final lines of the script are : - 

---- End output of pip install -r /vagrant/mtsw2e-requirements.txt ----
Ran pip install -r /vagrant/mtsw2e-requirements.txt returned 1
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.

I ssh'd onto the server and pip installed all the missing python libraries listed in mtsw2e...txt. 

ipython notebook

fires up an instance viewable on the server itself using lynx [also installed].

2014-04-01 20:35:30.807 [NotebookApp] The IPython Notebook is running at: http://127.0.0.1:8888/

The ipynb folder didn't make it through the install and back on the host os pointing a browser at localhost:8888 returns "No data received".

Any thoughts? I do have a working virtual box instance already for other things - I could install ipython notebook on there and copy the exercises on to that, but that would run counter to the beautiful simplicity of your proposed solution with Vagrant.

ptwobrussell commented 10 years ago

I would try to run "vagrant halt" followed by "vagrant provision" on the host and see how the guest responds. It should basically pick up where it left off, see that dependencies are satisfied, and just startup ipynb as expected.

When you say "the ipynb folder didn't make it through the install", what do you mean? On the host, you should have that folder from your Git checkout, and then Vagrant should sync that to the guest automatically when you "vagrant provision", so hopefully that won't be a problem. Still, I don't know how it would have disappeared in the first place, even if Chef failed, so I'll just preemptively point this out in advance as a potential pain point.

Let me know how that works. I'm sure we can keep this simple for you so that you can get to the good stuff.

bigdavejonnyt commented 10 years ago

Matthew,

Amazing what a difference a day can make! I went the vagrant destroy route, ran up again and I'm there. Mine was the confusion on the ipynb folder. I assumed it would form part of the vm build, although as soon as you mentioned syncing it reminded me I made the same wrong assumption at work recently.

So thanks - up and running.

Rgds

David