It looks like DB is not running.
Everything do on host machine where Vagrant is running.
Go with browser to http://192.168.33.10:8082 this is where H2 console is running. This way you can check if database is up.
You can also go to virtual machine with: vagrant ssh
When on machine do: ps –ef | grep java
This shows all java processes and one should be H2 database.
If not running start it manualy with commands described in:
https://github.com/eclipse/kapua/blob/develop/dev-tools/src/main/vagrant/README.MD
$ java -cp /usr/local/h2database/h2database-${H2DB_VERSION}/h2*.jar org.h2.tools.Server -baseDir /home/vagrant/H2/kapua
-webAllowOthers -tcpAllowOthers -tcpPort 3306 &
replace H2DB_VERSION with current version on box.
Hope it helps and hope we will switch to Docker soon
J
From: kapua-dev-bounces@xxxxxxxxxxx [mailto:kapua-dev-bounces@xxxxxxxxxxx]
On Behalf Of Alon Harel
Sent: Thursday, November 17, 2016 4:40 PM
To: kapua-dev@xxxxxxxxxxx
Subject: Re: [kapua-dev] Errors building Kapua
Hi,
I have managed to overcome the Vagrant issue by running 'rm /opt/vagrant/embedded/bin/curl' prior running 'start-demo.sh'.
However, now I get the following error:
[ERROR] Failed to execute goal org.codehaus.mojo:sql-maven-plugin:1.5:execute (create-schema) on project kapua-commons: Connection is broken: "java.net.ConnectException: Connection refused:
192.168.33.10:3306" [90067-192] -> [Help 1]
I can see that the VM (192.168.33.10) is answering pings though.
On Thu, Nov 17, 2016 at 3:39 PM, Alon Harel <alonhrl.us@xxxxxxxxx> wrote:
Hi Kapua community,
Creating base kapua box named trusty64/kapua-dev-box-0.1 ...
The box you requested to be removed could not be found. No
boxes named 'trusty64/kapua-dev-box-0.1' could be found.
/Users/alonharel/Documents/Work/kapua/dev-tools/src/main/vagrant/baseBox/kapua-box-tmp
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ubuntu/trusty64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
The box 'ubuntu/trusty64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below: