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

Installation issue #135

Closed gmalacar13 closed 10 years ago

gmalacar13 commented 10 years ago

Hi, I've cloned the repository and I'm stuck at the point where I have to change the vagrantfile settings for 32 bit system (I'm running Windows XP). According to the screencast i should type vim Vagrantfile which I do in gitbash but that opens a different terminal to the one in the screencast and the code within it is also different. I'm new to VMs, and vagrantfiles and boxes so not really sure how to edit the precise64 box to precise 32. Thanks in advance for any help, looking forward to mining some data!

ptwobrussell commented 10 years ago

Hi - thanks for reaching out for help. I'll do everything I can to get you past this issue so that you can get to the good stuff!

In the screencast, I used a special text editor called vim to edit the Vagrantfile, but you can use whatever text editor you'd like to achieve the same effect. For example, just open the Vagrantfile (which is just a text file) with notepad, make the change, save the file, and you'll be all set to continue on.

Make sense?

Let me know...

On Jan 29, 2014, at 3:48 PM, gmalacar13 notifications@github.com wrote:

Hi, I've cloned the repository and I'm stuck at the point where I have to change the vagrantfile settings for 32 bit system (I'm running Windows XP). According to the screencast i should type vim Vagrantfile which I do in gitbash but that opens a different terminal to the one in the screencast and the code within it is also different. I'm new to VMs, and vagrantfiles and boxes so not really sure how to edit the precise64 box to precise 32. Thanks in advance for any help, looking forward to mining some data!

— Reply to this email directly or view it on GitHub.

gmalacar13 commented 10 years ago

Thanks for your kind help! I edited the vagrantfile in notepad++ although the code read override.vm.box = precise64 instead of config.vm.box=precise32 in fact all instances of config appear as override in my vagrantfile Anyway I edited the 64 to 32 for box and box_url and went back to my mtsw directory to vagrant up The first time it stopped at apt22 (for at least half an hour) so then i did a destroy and vagrant up again and this time it seems to have stopped here (see attached code) Welcome to Git (version 1.8.5.2-preview20131230)

Run 'git help git' to display the help index. Run 'git help ' to display help for specific commands.

Giuseppe@PCG ~ $ cd Mining-the-Social-Web-2nd-Edition/

Giuseppe@PCG ~/Mining-the-Social-Web-2nd-Edition (master) $ vagrant up Bringing machine 'default' up with 'virtualbox' provider... [default] Clearing any previously set forwarded ports... There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "10525dc7-dce0-46e8-a6e2-55311582d29f", "--natpf1", "delet e", "ssh", "--natpf1", "delete", "tcp27017", "--natpf1", "delete", "tcp27018", " --natpf1", "delete", "tcp27019", "--natpf1", "delete", "tcp28017", "--natpf1", " delete", "tcp5000", "--natpf1", "delete", "tcp8888"]

Stderr: VBoxManage.exe: error: The machine 'Mining-the-Social-Web-2nd-Edition_de fault_1391039667750_75594' is already locked for a session (or being unlocked) VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), c omponent Machine, interface IMachine, callee IUnknown VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at lin e 462 of file VBoxManageModifyVM.cpp

Giuseppe@PCG ~/Mining-the-Social-Web-2nd-Edition (master) $ vagrant destroy Are you sure you want to destroy the 'default' VM? [y/N] y [default] Forcing shutdown of VM... [default] Destroying VM and associated drives... [default] Running cleanup tasks for 'chef_solo' provisioner...

Giuseppe@PCG ~/Mining-the-Social-Web-2nd-Edition (master) $ vagrant up Bringing machine 'default' up with 'virtualbox' provider... [default] Importing base box 'precise32'... [default] Matching MAC address for NAT networking... [default] Setting the name of the VM... [default] Clearing any previously set forwarded ports... [default] Clearing any previously set network interfaces... [default] Preparing network interfaces based on configuration... [default] Forwarding ports... [default] -- 22 => 2222 (adapter 1) [default] -- 8888 => 8888 (adapter 1) [default] -- 5000 => 5000 (adapter 1) [default] -- 27017 => 27017 (adapter 1) [default] -- 27018 => 27018 (adapter 1) [default] -- 27019 => 27019 (adapter 1) [default] -- 28017 => 28017 (adapter 1) [default] Running 'pre-boot' VM customizations... [default] Booting VM... [default] Waiting for machine to boot. This may take a few minutes... DL is deprecated, please use Fiddle [default] Machine booted and ready! [default] The guest additions on this VM do not match the installed version of VirtualBox! In most cases this is fine, but in rare cases it can prevent things such as shared folders from working properly. If you see shared folder errors, please make sure the guest additions within the virtual machine match the version of VirtualBox you have installed on your host and reload your VM.

Guest Additions Version: 4.2.0 VirtualBox Version: 4.3 [default] Mounting shared folders... [default] -- /vagrant [default] -- /tmp/vagrant-chef-1/chef-solo-1/cookbooks [default] Running provisioner: chef_solo... Generating chef JSON and uploading... Running chef-solo... stdin: is not a tty [2014-01-30T00:55:30+00:00] INFO: * Chef 10.14.2 * [2014-01-30T00:55:32+00:00] DEBUG: Building node object for precise32 [2014-01-30T00:55:32+00:00] DEBUG: Extracting run list from JSON attributes prov ided on command line [2014-01-30T00:55:32+00:00] INFO: Setting the run_list to ["recipe[mtsw2e::defau lt]"] from JSON [2014-01-30T00:55:32+00:00] DEBUG: Applying attributes from json file [2014-01-30T00:55:32+00:00] DEBUG: Platform is ubuntu version 12.04 [2014-01-30T00:55:32+00:00] INFO: Run List is [recipe[mtsw2e::default]] [2014-01-30T00:55:32+00:00] INFO: Run List expands to [mtsw2e::default] [2014-01-30T00:55:32+00:00] INFO: Starting Chef Run for precise32 [2014-01-30T00:55:32+00:00] INFO: Running start handlers [2014-01-30T00:55:32+00:00] INFO: Start handlers complete. [2014-01-30T00:55:32+00:00] DEBUG: No chefignore file found at /tmp/vagrant-chef -1/chef-solo-1/cookbooks/chefignore no files will be ignored [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook runit's library file: /tmp/v agrant-chef-1/chef-solo-1/cookbooks/runit/libraries/provider_runit_service.rb [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook runit's library file: /tmp/v agrant-chef-1/chef-solo-1/cookbooks/runit/libraries/default.rb [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook runit's library file: /tmp/v agrant-chef-1/chef-solo-1/cookbooks/runit/libraries/resource_runit_service.rb [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook apt's providers from /tmp/va grant-chef-1/chef-solo-1/cookbooks/apt/providers/preference.rb [2014-01-30T00:55:33+00:00] DEBUG: Loaded contents of /tmp/vagrant-chef-1/chef-s olo-1/cookbooks/apt/providers/preference.rb into a provider named apt_preference defined in Chef::Provider::AptPreference [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook apt's providers from /tmp/va grant-chef-1/chef-solo-1/cookbooks/apt/providers/repository.rb [2014-01-30T00:55:33+00:00] DEBUG: Loaded contents of /tmp/vagrant-chef-1/chef-s olo-1/cookbooks/apt/providers/repository.rb into a provider named apt_repository defined in Chef::Provider::AptRepository [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook yum's providers from /tmp/va grant-chef-1/chef-solo-1/cookbooks/yum/providers/repository.rb [2014-01-30T00:55:33+00:00] DEBUG: Loaded contents of /tmp/vagrant-chef-1/chef-s olo-1/cookbooks/yum/providers/repository.rb into a provider named yum_repository defined in Chef::Provider::YumRepository [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook yum's providers from /tmp/va grant-chef-1/chef-solo-1/cookbooks/yum/providers/key.rb [2014-01-30T00:55:33+00:00] DEBUG: Loaded contents of /tmp/vagrant-chef-1/chef-s olo-1/cookbooks/yum/providers/key.rb into a provider named yum_key defined in Ch ef::Provider::YumKey [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook python's providers from /tmp /vagrant-chef-1/chef-solo-1/cookbooks/python/providers/virtualenv.rb [2014-01-30T00:55:33+00:00] DEBUG: Loaded contents of /tmp/vagrant-chef-1/chef-s olo-1/cookbooks/python/providers/virtualenv.rb into a provider named python_virt ualenv defined in Chef::Provider::PythonVirtualenv [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook python's providers from /tmp /vagrant-chef-1/chef-solo-1/cookbooks/python/providers/pip.rb [2014-01-30T00:55:33+00:00] DEBUG: Loaded contents of /tmp/vagrant-chef-1/chef-s olo-1/cookbooks/python/providers/pip.rb into a provider named python_pip defined in Chef::Provider::PythonPip [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook apt's resources from /tmp/va grant-chef-1/chef-solo-1/cookbooks/apt/resources/preference.rb [2014-01-30T00:55:33+00:00] DEBUG: Loaded contents of /tmp/vagrant-chef-1/chef-s olo-1/cookbooks/apt/resources/preference.rb into a resource named apt_preference defined in Chef::Resource::AptPreference [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook apt's resources from /tmp/va grant-chef-1/chef-solo-1/cookbooks/apt/resources/repository.rb [2014-01-30T00:55:33+00:00] DEBUG: Loaded contents of /tmp/vagrant-chef-1/chef-s olo-1/cookbooks/apt/resources/repository.rb into a resource named apt_repository defined in Chef::Resource::AptRepository [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook yum's resources from /tmp/va grant-chef-1/chef-solo-1/cookbooks/yum/resources/key.rb [2014-01-30T00:55:33+00:00] DEBUG: Loaded contents of /tmp/vagrant-chef-1/chef-s olo-1/cookbooks/yum/resources/key.rb into a resource named yum_key defined in Ch ef::Resource::YumKey [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook yum's resources from /tmp/va grant-chef-1/chef-solo-1/cookbooks/yum/resources/repository.rb [2014-01-30T00:55:33+00:00] DEBUG: Loaded contents of /tmp/vagrant-chef-1/chef-s olo-1/cookbooks/yum/resources/repository.rb into a resource named yum_repository defined in Chef::Resource::YumRepository [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook python's resources from /tmp /vagrant-chef-1/chef-solo-1/cookbooks/python/resources/pip.rb [2014-01-30T00:55:33+00:00] DEBUG: Loaded contents of /tmp/vagrant-chef-1/chef-s olo-1/cookbooks/python/resources/pip.rb into a resource named python_pip defined in Chef::Resource::PythonPip [2014-01-30T00:55:33+00:00] DEBUG: Loading cookbook python's resources from /tmp /vagrant-chef-1/chef-solo-1/cookbooks/python/resources/virtualenv.rb [2014-01-30T00:55:33+00:00] DEBUG: Loaded contents of /tmp/vagrant-chef-1/chef-s olo-1/cookbooks/python/resources/virtualenv.rb into a resource named python_virt ualenv defined in Chef::Resource::PythonVirtualenv [2014-01-30T00:55:33+00:00] DEBUG: Node precise32 loading cookbook apt's attribu te file /tmp/vagrant-chef-1/chef-solo-1/cookbooks/apt/attributes/default.rb [2014-01-30T00:55:33+00:00] DEBUG: Node precise32 loading cookbook yum's attribu te file /tmp/vagrant-chef-1/chef-solo-1/cookbooks/yum/attributes/epel.rb [2014-01-30T00:55:33+00:00] DEBUG: Node precise32 loading cookbook yum's attribu te file /tmp/vagrant-chef-1/chef-solo-1/cookbooks/yum/attributes/elrepo.rb [2014-01-30T00:55:33+00:00] DEBUG: Node precise32 loading cookbook yum's attribu te file /tmp/vagrant-chef-1/chef-solo-1/cookbooks/yum/attributes/remi.rb [2014-01-30T00:55:33+00:00] DEBUG: Node precise32 loading cookbook yum's attribu te file /tmp/vagrant-chef-1/chef-solo-1/cookbooks/yum/attributes/default.rb [2014-01-30T00:55:33+00:00] DEBUG: Node precise32 loading cookbook build-essenti al's attribute file /tmp/vagrant-chef-1/chef-solo-1/cookbooks/build-essential/at tributes/default.rb [2014-01-30T00:55:33+00:00] DEBUG: Node precise32 loading cookbook runit's attri bute file /tmp/vagrant-chef-1/chef-solo-1/cookbooks/runit/attributes/default.rb [2014-01-30T00:55:33+00:00] DEBUG: Node precise32 loading cookbook python's attr ibute file /tmp/vagrant-chef-1/chef-solo-1/cookbooks/python/attributes/default.r b [2014-01-30T00:55:33+00:00] DEBUG: Loading Recipe mtsw2e::default via include_re cipe [2014-01-30T00:55:33+00:00] DEBUG: Found recipe default in cookbook mtsw2e [2014-01-30T00:55:33+00:00] DEBUG: Loading Recipe apt via include_recipe [2014-01-30T00:55:33+00:00] DEBUG: Found recipe default in cookbook apt [2014-01-30T00:55:33+00:00] DEBUG: Loading Recipe runit via include_recipe [2014-01-30T00:55:33+00:00] DEBUG: Found recipe default in cookbook runit [2014-01-30T00:55:33+00:00] DEBUG: Loading Recipe python via include_recipe [2014-01-30T00:55:33+00:00] DEBUG: Found recipe default in cookbook python [2014-01-30T00:55:33+00:00] DEBUG: Loading Recipe python::package via include_re cipe [2014-01-30T00:55:33+00:00] DEBUG: Found recipe package in cookbook python [2014-01-30T00:55:34+00:00] DEBUG: Loading Recipe python::pip via include_recipe

[2014-01-30T00:55:34+00:00] DEBUG: Found recipe pip in cookbook python [2014-01-30T00:55:34+00:00] DEBUG: Loading Recipe python::virtualenv via include _recipe [2014-01-30T00:55:34+00:00] DEBUG: Found recipe virtualenv in cookbook python [2014-01-30T00:55:34+00:00] DEBUG: I am not loading python::pip, because I have already seen it. [2014-01-30T00:55:34+00:00] DEBUG: Loading from cookbook_path: /tmp/vagrant-chef -1/chef-solo-1/cookbooks [2014-01-30T00:55:34+00:00] DEBUG: Converging node precise32 [2014-01-30T00:55:34+00:00] INFO: Processing execute[apt-get-update] action run (apt::default line 22) [2014-01-30T00:56:08+00:00] INFO: execute[apt-get-update] ran successfully [2014-01-30T00:56:08+00:00] INFO: Processing execute[apt-get update] action noth ing (apt::default line 29) [2014-01-30T00:56:08+00:00] DEBUG: Doing nothing for execute[apt-get update] [2014-01-30T00:56:08+00:00] INFO: Processing execute[apt-get autoremove] action nothing (apt::default line 36) [2014-01-30T00:56:08+00:00] DEBUG: Doing nothing for execute[apt-get autoremove]

[2014-01-30T00:56:08+00:00] INFO: Processing execute[apt-get autoclean] action n othing (apt::default line 42) [2014-01-30T00:56:08+00:00] DEBUG: Doing nothing for execute[apt-get autoclean] [2014-01-30T00:56:08+00:00] INFO: Processing package[update-notifier-common] act ion install (apt::default line 48) [2014-01-30T00:56:08+00:00] DEBUG: package[update-notifier-common] checking pack age status for update-notifier-common [2014-01-30T00:56:08+00:00] DEBUG: package[update-notifier-common] current versi on is nil [2014-01-30T00:56:08+00:00] DEBUG: package[update-notifier-common] candidate ver sion is 0.119ubuntu8.6 [2014-01-30T00:56:08+00:00] DEBUG: Executing apt-get -q -y install update-notifi er-common=0.119ubuntu8.6

gmalacar13 commented 10 years ago

That was at least 20 minutes ago so I think the installation will not complete

ptwobrussell commented 10 years ago

@gmalacar13 - I'm very sorry for the delay on getting back to this issue. It looks as though the output you provided is truncated. The last line that shows appears to be fine, though I take it from your follow up comment that something was hanging or timed out or an error occurred. Could you provide me with a full output. A link to a pastebin might work well for something like this.

It appears as though you've made the right changes to your Vagrantfile and the issue (from what I can surmise) might be that some of the downloads are slow and causing issues with timeouts and such? Anytime you see something error out that might be related to a network issue, your safest bet is to follow up with a "vagrant provision" command, which essentially tells Vagrant to pick back up and try again. In many circumstances, this has helped a lot of people get past quirky issues during the initial bootstrap.

Let me know. I'm here to help.

gmalacar13 commented 10 years ago

No worries about delay, I haven't had time to look at it again anyway. Thanks for your reply, I will give it another go asap and let you know, provision trick sounds useful, if it fails again will send full code.

Sent from my HTC

----- Reply message ----- From: "Matthew A. Russell" notifications@github.com To: "ptwobrussell/Mining-the-Social-Web-2nd-Edition" Mining-the-Social-Web-2nd-Edition@noreply.github.com Cc: "gmalacar13" gmalacarne13@gmail.com Subject: [Mining-the-Social-Web-2nd-Edition] Installation issue (#135) Date: Thu, Feb 6, 2014 14:22 @gmalacar13 - I'm very sorry for the delay on getting back to this issue. It looks as though the output you provided is truncated. The last line that shows appears to be fine, though I take it from your follow up comment that something was hanging or timed out or an error occurred. Could you provide me with a full output. A link to a pastebin might work well for something like this.

It appears as though you've made the right changes to your Vagrantfile and the issue (from what I can surmise) might be that some of the downloads are slow and causing issues with timeouts and such? Anytime you see something error out that might be related to a network issue, your safest bet is to follow up with a "vagrant provision" command, which essentially tells Vagrant to pick back up and try again. In many circumstances, this has helped a lot of people get past quirky issues during the initial bootstrap.

Let me know. I'm here to help.

— Reply to this email directly or view it on GitHub.

ptwobrussell commented 10 years ago

Any luck? If not, just let me know that you're all squared away so I can rest easy :)

gmalacar13 commented 10 years ago

Thanks for checking back (again), unfortunately when I gave it another shot last weekend I had problems with disk space so it never finished installing the vm. I installed virtual box and vagrant on my D drive where I have space but the vagrant folder and others automatically get placed on my C drive. Going to see if I can find a workaround when I have time (maybe tomorrow). Please rest easy until I find time to get back to it, I will let you know for sure if I manage.

On 14 February 2014 14:59, Matthew A. Russell notifications@github.comwrote:

Any luck? If not, just let me know that you're all squared away so I can rest easy :)

Reply to this email directly or view it on GitHubhttps://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition/issues/135#issuecomment-35090532 .