nhhagen / vagrant-solr-box

Vagrant Solr box to get a Solr environment quickly up and running in a VM. If you plan to modify the Solr configuration copy the content of this repo to a new repo.
MIT License
18 stars 34 forks source link

Problem with vagrant up #5

Open funderburkjim opened 9 years ago

funderburkjim commented 9 years ago

Hi - I was directed to this github by a google search for 'vagrant solr box'. There was some problem after the precise64 box was downloaded. Any suggestions how to fix this? Here's the log of the 'vagrant up' session. I am running it in the 'cmd' windown in Windows 7:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Jim>cd vagrant

C:\Users\Jim\vagrant>cd vagrant-solr-box-master

C:\Users\Jim\vagrant\vagrant-solr-box-master>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'precise64' could not be found. Attempting to find and install.
..
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Adding box 'precise64' (v0) for provider: virtualbox
    default: Downloading: http://files.vagrantup.com/precise64.box
    default: Progress: 100% (Rate: 347k/s, Estimated time remaining: --:--:--)
==> default: Successfully added box 'precise64' (v0) for 'virtualbox'!
==> default: Importing base box 'precise64'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: vagrant-solr-box-master_default_1422298
916919_10394
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 8983 => 8983 (adapter 1)
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version o
f
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you
 see
    default: shared folder errors, please make sure the guest additions within t
he
    default: virtual machine match the version of VirtualBox you have installed
on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 4.2.0
    default: VirtualBox Version: 4.3
==> default: Mounting shared folders...
    default: /vagrant => C:/Users/Jim/vagrant/vagrant-solr-box-master
    default: /tmp/vagrant-puppet-4/manifests => C:/Users/Jim/vagrant/vagrant-sol
r-box-master/manifests
    default: /tmp/vagrant-puppet-4/modules-0 => C:/Users/Jim/vagrant/vagrant-sol
r-box-master/modules
==> default: Running provisioner: puppet...
==> default: Running Puppet with default.pp...
==> default: stdin: is not a tty
==> default: Could not find class apt for precise64.myhome.westell.com at /tmp/v
agrant-puppet-4/manifests/default.pp:10 on node precise64.myhome.westell.com
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

puppet apply --modulepath '/tmp/vagrant-puppet-4/modules-0:/etc/puppet/modules'
--color=false --manifestdir /tmp/vagrant-puppet-4/manifests --detailed-exitcodes
 /tmp/vagrant-puppet-4/manifests/default.pp

Stdout from the command:

Stderr from the command:

stdin: is not a tty
Could not find class apt for precise64.myhome.westell.com at /tmp/vagrant-puppet
-4/manifests/default.pp:10 on node precise64.myhome.westell.com

C:\Users\Jim\vagrant\vagrant-solr-box-master>
nhhagen commented 9 years ago

Have you made sude that the git submodules are cloned?

gabrielnic commented 8 years ago

Hello, Had the same problem, this problem appears if you are using virtualbox 5.x. Use version 4.x

alexmc6 commented 8 years ago

Just had the same problem. It was not clear that I had to do a

git clone --recursive URL_TO_REPO

though the README does say so.

The problem is not Virtualbox V5.