| Re: [kapua-dev] failing on installing Kapua |
Hi Alberto,The mentioned setup is the only one I've tried (ubuntu 16.04 either on a physical machine and a virtual machine).I do have a macOS. I will try to run it from there as well with the base-box and develop machine and let you know.Thanks,Yuval.On Thu, Jan 5, 2017 at 12:41 PM, Codutti, Alberto <Alberto.Codutti@xxxxxxxxxxxx> wrote:Hi Yuval ,
I worked on this a bit more today but I had no luck.
My current set up is a physical macOS, and it is working with the Develop Box machine and Base Box.
Demo box is currently broken.
|| ive also had the same failure while running direct on ubuntu (not only inside vb ubuntu image)
You tried on an actual installation or some other virtualized env (ie: AWS)?
I’m trying to guess if it is something related to the virtualization support on a virtualized environment.
Unfortunately, I have no chance to use a physical Linux machine right now.
Regards,
Alberto Codutti | R&D | EUROTECH | direct: +39 0433 485412 | Timezone: CET (UTC +01:00)
From: <kapua-dev-bounces@xxxxxxxxxxx
> on behalf of Yuval Zohar <yuvzohar@xxxxxxxxx>
Reply-To: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Date: Wednesday, January 4, 2017 at 5:27 PM
To: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Subject: Re: [kapua-dev] failing on installing Kapua
hi Alberto,
thanks for your response.
can u recommand on a setup which contantly works for you.
btw
ive also had the same failure while running direct on ubuntu (not only inside vb ubuntu image)
thanks
On 4 Jan 2017 6:20 pm, "Codutti, Alberto" <Alberto.Codutti@xxxxxxxxxxxx> wrote:
Hi Yuval,
I’ve worked a bit on your issue and iI got the same error while trying to run Vagrant+VirtualBox inside a Virtual Box VM, which seems your set up.
I’ve found several post that report that is not possible. I’ve also found some posts that says that this is possible.
So far I was not able to find a working configuration.
I’ll continue investigate on this and I’ll open a GitHub issue to track this problem.
Regards,
Alberto
From: <kapua-dev-bounces@xxxxxxxxxxx
> on behalf of Yuval Zohar <yuvzohar@xxxxxxxxx>
Reply-To: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Date: Wednesday, January 4, 2017 at 2:06 PM
To: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Subject: Re: [kapua-dev] failing on installing Kapua
Hi,
I've tried to install again on 2 more ubuntu machines with clean setup but it didnt help.
attached is a video with the process of running the develop vagrant machine (after creating base-box) but as can be seen from the video , the develop vagrant device is running inside virtualbox but , it cannot be access from the script (vagrant ssh) and after a few minuets there's a timeout message (attached file).
are there any suggestions ?
is there going to be any script release any soon which might solve those issues ?
thanks,
yuval
On Tue, Jan 3, 2017 at 8:42 PM, Pablo Chacin <pablochacin@xxxxxxxxx> wrote:
After several attempts, just repeating the same steps (and removing manually the VBox's files) I got it to work. Here is the sequence of events in a successful build:
==> default: Attempting graceful shutdown of VM...
==> default: Clearing any previously set forwarded ports...
==> default: Exporting VM...
==> default: Compressing package to: /home/pablo/workspace/kapua/de
v-tools/src/main/vagrant/baseB ox/kapua-box-tmp/trusty64- kapua-dev-0.1.box ==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'trusty64/kapua-dev-box-0.1' (v0) for provider:
box: Unpacking necessary files from: file:///home/pablo/workspace/k
apua/dev-tools/src/main/vagran t/baseBox/kapua-box-tmp/trusty 64-kapua-dev-0.1.box ==> box: Successfully added box 'trusty64/kapua-dev-box-0.1' (v0) for 'virtualbox'!
==> default: Destroying VM and associated drives...
... done.
creating demo vagrant machine
======> start demo vagrant machine
======> destroy old machine
==> default: VM not created. Moving on...
======> delete old Vagrant file
======> kapua vagrant demo machine... starting
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'trusty64/kapua-dev-box-0.1'..
. ==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: demo
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 3306 (guest) => 3306 (host) (adapter 1)
default: 1883 (guest) => 1883 (host) (adapter 1)
default: 8883 (guest) => 8883 (host) (adapter 1)
default: 5005 (guest) => 5005 (host) (adapter 1)
default: 9300 (guest) => 9300 (host) (adapter 1)
default: 9200 (guest) => 9200 (host) (adapter 1)
default: 8080 (guest) => 8080 (host) (adapter 1)
default: 8443 (guest) => 8443 (host) (adapter 1)
default: 8000 (guest) => 8000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (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 of
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 the
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.3.36
default: VirtualBox Version: 5.0
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
default: /kapua => /home/pablo/workspace/kapua
default: /vagrant => /home/pablo/workspace/kapua/de
v-tools/src/main/vagrant ==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: TCP server running at tcp://10.0.2.15:3306 (others can connect)
==> default: PG server running at pg://10.0.2.15:5435 (only local connections)
==> default: Web Console server running at http://10.0.2.15:8082 (others can connect)
==> default: (Update count: 0, 6 ms)
==> default: (Update count: 0, 2 ms)
==> default: (Update count: 0, 2 ms)
==> default: Failed to start a browser to open the URL http://10.0.2.15:8082: Browser detection failed and system property h2.browser not set
======> kapua vagrant demo machine... starting DONE
======> please type 'vagrant ssh' to connect to the machine.
======> Follow the instructions to deploy the kapua components into the machine
On Tue, Jan 3, 2017 at 6:43 PM, Pablo Chacin <pablochacin@xxxxxxxxx> wrote:
I have also experienced this error in a more or less random way. I've tracked it to the sequence of events related to the vm creation process listed below. My understanding is that it is due to race condition between the preparation of the vm and the kapua build process. In between the vm is stopped and then started, but sometimes this process doesn't work as expected:
==> default: Attempting graceful shutdown of VM...
==> default: Clearing any previously set forwarded ports...
==> default: Exporting VM...
==> default: Compressing package to: /home/pablo/workspace/kapua/de
v-tools/src/main/vagrant/baseB ox/kapua-box-tmp/trusty64- kapua-dev-0.1.box ==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'trusty64/kapua-dev-box-0.1' (v0) for provider:
box: Unpacking necessary files from: file:///home/pablo/workspace/k
apua/dev-tools/src/main/vagran t/baseBox/kapua-box-tmp/trusty 64-kapua-dev-0.1.box ==> box: Successfully added box 'trusty64/kapua-dev-box-0.1' (v0) for 'virtualbox'!
==> default: Destroying VM and associated drives...
... done.
creating demo vagrant machine
======> start demo vagrant machine
======> destroy old machine
==> default: VM not created. Moving on...
======> delete old Vagrant file
======> kapua vagrant demo machine... starting
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'trusty64/kapua-dev-box-0.1'..
. ==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: demo
The name of your virtual machine couldn't be set because VirtualBox
is reporting another VM with that name already exists. Most of the
time, this is because of an error with VirtualBox not cleaning up
properly. To fix this, verify that no VMs with that name do exist
(by opening the VirtualBox GUI). If they don't, then look at the
folder in the error message from VirtualBox below and remove it
if there isn't any information you need in there.
VirtualBox error:
VBoxManage: error: Could not rename the directory '/home/pablo/VirtualBox VMs/kapua-box-tmp_default_1483
464707091_60906_1483464959294_ 527' to '/home/pablo/VirtualBox VMs/demo' to save the settings file (VERR_ALREADY_EXISTS) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "SaveSettings()" at line 3016 of file VBoxManageModifyVM.cpp
On Mon, Jan 2, 2017 at 12:32 PM, Alon Harel <alonhrl.us@xxxxxxxxx> wrote:
Hi Yuval,
I had the same issues, the problem is with the Vagrant setup as Stefano mentioned. I had to try many advises in the web for solving that. I think that what eventually helped is deleting some vagrant files.
Keep trying, for me it took few days...
Good luck,
Alon
On Sat, Dec 31, 2016 at 2:46 PM, Morson, Stefano <stefano.morson@xxxxxxxxxxxx> wrote:
In order to proceed step by step you may be interested to run the pieces individually.
In this case you can take a look at the following guide:
https://github.com/eclipse/kap
ua/tree/develop/dev-tools/src/ main/vagrant
Best wishes to you,
Stefano
From: kapua-dev-bounces@xxxxxxxxxxx <kapua-dev-bounces@xxxxxxxxxxx
> on behalf of Yuval Zohar <yuvzohar@xxxxxxxxx>
Sent: Saturday, December 31, 2016 12:12:55 PM
To: kapua developer discussions
Subject: Re: [kapua-dev] failing on installing Kapua
hi stefano,
thanks.
ill give it a try later on and let u know.
happy new year!
On 31 Dec 2016 13:08, "Morson, Stefano" <stefano.morson@xxxxxxxxxxxx> wrote:
Hi,
the error
shows that the maven build is not able to connect to H2 db instance which, in the case of the demo instance, is supposed to be running within the virtual machine (managed through Vagrant). This can happen for several reasons, the virtual machine has not been started, the tcp/ip ports are already in use, etc...
The maven command underneath is listed within the shell script:
"../kapua-develop/dev-tools/sr
c/main/bin/start-demo.sh"
and is the following:
$>mvn clean install -Psql -Pdeploy
so to execute the suggestion run the following:
$>mvn clean install -e -Psql -Pdeploy
from the kapua source root directory.
Regards,
Stefano
From: kapua-dev-bounces@xxxxxxxxxxx <kapua-dev-bounces@xxxxxxxxxxx
> on behalf of Yuval Zohar <yuvzohar@xxxxxxxxx>
Sent: Thursday, December 29, 2016 1:49 PM
To: kapua developer discussions
Subject: Re: [kapua-dev] failing on installing Kapua
hi,
ive deleted everything under ".vagrant.d" and rerun the "../kapua-develop/dev-tool
s/src/main/bin/start-demo.sh" script once again :
FO] kapua-security-authentication-
api .................. SUCCESS [ 0.898 s] VM must be running to open SSH connection. Run `vagrant up`
[INFO] kapua-commons ...................................... FAILURE [ 5.565 s]
[INFO] kapua-locator ...................................... SKIPPED
[INFO] kapua-guice ........................................ SKIPPED
[INFO] kapua-user ......................................... SKIPPED
[INFO] kapua-user-api ..................................... SKIPPED
[INFO] kapua-account ...................................... SKIPPED
[INFO] kapua-account-api .................................. SKIPPED
[INFO] kapua-test ......................................... SKIPPED
[INFO] kapua-security-shiro ............................... SKIPPED
[INFO] kapua-message ...................................... SKIPPED
[INFO] kapua-message-api .................................. SKIPPED
[INFO] kapua-datastore .................................... SKIPPED
[INFO] kapua-datastore-api ................................ SKIPPED
[INFO] kapua-message-internal ............................. SKIPPED
[INFO] kapua-datastore-internal ........................... SKIPPED
[INFO] kapua-device ....................................... SKIPPED
[INFO] kapua-device-api ................................... SKIPPED
[INFO] kapua-device-registry .............................. SKIPPED
[INFO] kapua-device-registry-api .......................... SKIPPED
[INFO] kapua-transport .................................... SKIPPED
[INFO] kapua-transport-api ................................ SKIPPED
[INFO] kapua-device-call .................................. SKIPPED
[INFO] kapua-device-call-api .............................. SKIPPED
[INFO] kapua-translator ................................... SKIPPED
[INFO] kapua-translator-api ............................... SKIPPED
[INFO] kapua-device-call-kura ............................. SKIPPED
[INFO] kapua-device-commons ............................... SKIPPED
[INFO] kapua-transport-mqtt ............................... SKIPPED
[INFO] kapua-translator-kura .............................. SKIPPED
[INFO] kapua-translator-kura-mqtt ......................... SKIPPED
[INFO] kapua-device-call-test ............................. SKIPPED
[INFO] kapua-device-configuration ......................... SKIPPED
[INFO] kapua-device-configuration-api ..................... SKIPPED
[INFO] kapua-device-configuration-internal ................ SKIPPED
[INFO] kapua-device-packages .............................. SKIPPED
[INFO] kapua-device-packages-api .......................... SKIPPED
[INFO] kapua-device-packages-internal ..................... SKIPPED
[INFO] kapua-user-internal ................................ SKIPPED
[INFO] kapua-device-registry-internal ..................... SKIPPED
[INFO] kapua-device-bundle ................................ SKIPPED
[INFO] kapua-device-bundle-api ............................ SKIPPED
[INFO] kapua-device-bundle-internal ....................... SKIPPED
[INFO] kapua-device-command ............................... SKIPPED
[INFO] kapua-device-command-api ........................... SKIPPED
[INFO] kapua-device-command-internal ...................... SKIPPED
[INFO] kapua-account-internal ............................. SKIPPED
[INFO] kapua-device-command-test .......................... SKIPPED
[INFO] kapua-transport-jms ................................ SKIPPED
[INFO] kapua-transport-test ............................... SKIPPED
[INFO] kapua-translator-kapua ............................. SKIPPED
[INFO] kapua-translator-kapua-kura ........................ SKIPPED
[INFO] kapua-translator-kura-jms .......................... SKIPPED
[INFO] kapua-broker-core .................................. SKIPPED
[INFO] kapua-console ...................................... SKIPPED
[INFO] kapua-rest-api ..................................... SKIPPED
[INFO] kapua-assembly ..................................... SKIPPED
[INFO] kapua-dev-tools .................................... SKIPPED
[INFO] ------------------------------------------------------------ ------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------ ------------
[INFO] Total time: 18.994 s
[INFO] Finished at: 2016-12-29T14:39:15+02:00
[INFO] Final Memory: 43M/577M
[INFO] ------------------------------------------------------------ ------------
[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.SocketTimeoutExcepti on: connect timed out: 192.168.33.10:3306" [90067-192] -> [Help 1
]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecuti onException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :kapua-commons
to start the virtual machine.
[*** IVE TYPED vagrant up ***]
yuval@zmaor-kubuntu:~/Development/Wireless/IoT/Eclipse/ A Vagrant environment or target machine is required to run thisClouds/framework/kapua- develop/dev-tools/src/main/ bin$ vagrant up
command. Run `vagrant init` to create a new Vagrant environment. Or,
get an ID of a target machine from `vagrant global-status` to run
this command on. A final option is to change to a directory with a
Vagrantfile and to try again.
[*** IVE TYPED vagrant init ***]
yuval@zmaor-kubuntu:~/Developm
ent/Wireless/IoT/Eclipse/ Clouds/framework/kapua- develop/dev-tools/src/main/ bin$ vagrant init
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
it says : "To see the full stack trace of the errors, re-run Maven with the -e switch.Re-run Maven using the -X switch to enable full debug logging."
i'm not a maven expert, what should i type in order to see the full trace ?
"mvn -e" ?
"mvn -Xe" ?
thanks
On Thu, Dec 29, 2016 at 2:21 PM, Mezzasalma, Claudio <Claudio.Mezzasalma@eurotech.c
om > wrote:By reading the log it seems that there’s something wrong with the downloaded VirtualBox image:
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Could not create the imported medium '/home/yuval/VirtualBox VMs/ubuntu-cloudimg-trusty-vag
rant-amd64_1482941047842_69109 /box-disk1.vmdk'. VBoxManage: error: VMDK: Compressed image is corrupted '/home/yuval/.vagrant.d/boxes/
ubuntu-VAGRANTSLASH-trusty64/2 0161214.0.0/virtualbox/box-dis k1.vmdk' (VERR_ZIP_CORRUPTED) VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerA
rg*)" at line 877 of file VBoxManageAppliance.cpp
Have you tried cleaning up the .vagrant.d folder under your home (beware of any other vagrant boxes you may have!) and running the script again to redownload the base box?
--
Claudio Mezzasalma | Eurotech
Da: <kapua-dev-bounces@xxxxxxxxxxx
> per conto di Yuval Zohar <yuvzohar@xxxxxxxxx>
Risposta: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Data: mercoledì 28 dicembre 2016 17:42
A: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Oggetto: Re: [kapua-dev] failing on installing Kapua
Hi,
Thanks for your response.
Yes, I've downloaded the zip file (kapua-develop) from https://github.com/eclipse/ka
pua with develop branch.
I've followed the instructions for the "demo machine quick start" :
$ cd $KAPUA_GITHUB_HOME_DIR/dev-tools/src/main/bin $ ./start-demo.shI think all the problems refers to the vagrant VM (as i recall i had to install it manually on the linux machine but it didnt help to solve the problem).
attached is the log file
On Wed, Dec 28, 2016 at 5:24 PM, Mezzasalma, Claudio <Claudio.Mezzasalma@eurotech.c
om > wrote:Hello Yuval,
Are you trying to run the script on the develop branch? If so, do you have any detailed error log when the compilation is failing?
--
Claudio Mezzasalma | Eurotech
Da: <kapua-dev-bounces@xxxxxxxxxxx
> per conto di Yuval Zohar <yuvzohar@xxxxxxxxx>
Risposta: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Data: mercoledì 28 dicembre 2016 15:27
A: "kapua-dev@xxxxxxxxxxx" <kapua-dev@xxxxxxxxxxx>
Oggetto: [kapua-dev] failing on installing Kapua
Hello ,
We're trying to install Kapua on a Kubuntu machine by following instructions from both github's README :
and Kapua's site : https://www.eclipse.org/kapu
a/getting-started.php
Unfortunately, running the scripts keep falling.
O] kapua ..............................
................ SUCCESS [ 1.356 s]
[INFO] kapua-service ...................................... SUCCESS [ 0.007 s]
[INFO] kapua-service-api .................................. SUCCESS [ 5.280 s]
[INFO] kapua-security ..................................... SUCCESS [ 0.012 s]
[INFO] kapua-security-authorization ....................... SUCCESS [ 0.020 s]
[INFO] kapua-security-authorization-api ................... SUCCESS [ 0.517 s]
[INFO] kapua-security-authentication ...................... SUCCESS [ 0.007 s]
[INFO] kapua-security-authentication-api .................. SUCCESS [ 0.174 s]
[INFO] kapua-commons ...................................... FAILURE [ 4.147 s]
is there any detailed documentation or a step-by-step youtube guide which explains what to do ?
thanks,
yuval.
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev
--
Pablo Chacin
--
Pablo Chacin
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev
Attachment:
Screen Shot 2017-01-05 at 17.05.11.png
Description: PNG image
