VDKv2 OpenIoT Release 0.6.1 Virtual Box Setup Guide: problem deploying

58 views
Skip to first unread message

Nick Decroos

unread,
Sep 14, 2016, 9:08:06 AM9/14/16
to OpenIoT
I'm following these instructions to install OpenIoT release 0.6.1 with VirtualBox : https://github.com/OpenIotOrg/openiot/wiki/VDKv2---OpenIoT-Release-0.6.1---Virtual-Box-Setup-Guide.
I'm running into some troubles.

When I execute
./virtuoso_start.sh
I get:
22:08:10 { Loading plugin 1: Type `plain', file `wikiv' in `/media/openiot/virtuoso-opensource-7/lib/virtuoso/hosting'
22:08:10 FAILED plugin 1: Unable to locate file }
22:08:10 { Loading plugin 2: Type `plain', file `mediawiki' in `/media/openiot/virtuoso-opensource-7/lib/virtuoso/hosting'
22:08:10 FAILED plugin 2: Unable to locate file }
22:08:10 { Loading plugin 3: Type `plain', file `creolewiki' in `/media/openiot/virtuoso-opensource-7/lib/virtuoso/hosting'
22:08:10 FAILED plugin 3: Unable to locate file }
22:08:10 OpenLink Virtuoso Universal Server
22:08:10 Version 07.10.3211-pthreads for Linux as of Aug 18 2014
22:08:10 uses parts of OpenSSL, PCRE, Html Tidy
22:08:11 Database version 3126
22:08:11 SQL Optimizer enabled (max 1000 layouts)
22:08:13 Compiler unit is timed at 0.000451 msec
22:08:15 built-in procedure "repl_undot_name" overruled by the RDBMS
22:08:16 Roll forward started
22:08:16 Roll forward complete
22:08:17 Checkpoint started
22:08:17 Checkpoint finished, log reused
22:08:17 HTTP/WebDAV server online at 8890
22:08:17 Server online at 1111 (pid 3342)

localhost:8890 still works. I've read that you can only continue with starting JBoss if virtuoso runs without errors.
Is this output still OK?
Furthermore, ./jboss_cli.sh should be ./jboss-cli.sh.

Just before I execute the first deploy command, my last output in the terminal for JBoss is:
22:35:26,826 INFO [stdout] (scheduler_Worker-8) 22:35:26.826 [scheduler_Worker-8] INFO o.o.s.o.OpenIoTServicesManagerImpl - Loaded 10 services.

So there are 10 services loaded.

When I execute the first deploy command

deploy /media/openiot/openiot-code/modules/lsm-light/lsm-light.server/target/lsm-light.server.war --force
I get:

22:37:05,258 INFO [org.jboss.as.repository] (management-handler-thread - 5) JBAS014900: Content added at location /media/openiot/jboss-as-7.1.1.Final/standalone/data/content/e1/834b9697346cf974a55f5d23d0c07d80072f97/content
22:37:06,933 INFO [stdout] (MSC service thread 1-5) 22:37:06.932 [MSC service thread 1-5] DEBUG net.bull.javamelody - JavaMelody filter destroy done in 1227 ms
22:37:07,009 INFO [stdout] (MSC service thread 1-5) 22:37:07.009 [MSC service thread 1-5] DEBUG net.bull.javamelody - JavaMelody listener destroy done
22:37:07,012 INFO [stdout] (MSC service thread 1-5) 22:37:07.012 [MSC service thread 1-5] INFO o.o.lsm.pooling.ConnectionManager - contextDestroyed....
22:37:07,015 INFO [stdout] (MSC service thread 1-5) 22:37:07.015 [MSC service thread 1-5] INFO com.jolbox.bonecp.BoneCP - Shutting down connection pool...
22:37:07,059 INFO [stdout] (MSC service thread 1-5) 22:37:07.059 [MSC service thread 1-5] INFO com.jolbox.bonecp.BoneCP - Connection pool has been shutdown.
22:37:07,062 INFO [stdout] (MSC service thread 1-5) 22:37:07.061 [MSC service thread 1-5] INFO o.o.lsm.pooling.ConnectionManager - contextDestroyed.....Connection Pooling shut downed!
22:37:08,849 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment lsm-light.server.war in 3334ms
22:37:08,858 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "lsm-light.server.war"
22:37:26,691 INFO [stdout] (scheduler_Worker-9) 22:37:26.376 [scheduler_Worker-9] INFO o.o.s.o.OpenIoTServicesManagerImpl - Reloading registered services.
22:37:26,896 INFO [stdout] (scheduler_Worker-9) 22:37:26.895 [scheduler_Worker-9] INFO o.o.s.o.l.LSMServiceRegistryDaoImpl - Reloading registered services ...
22:37:32,402 INFO [stdout] (scheduler_Worker-9) Server returned non-OK code: 404
22:37:32,413 INFO [stdout] (scheduler_Worker-9) Server returned non-OK code: 404
22:37:32,437 INFO [stdout] (scheduler_Worker-9) Server returned non-OK code: 404
22:37:32,443 INFO [stdout] (scheduler_Worker-9) Server returned non-OK code: 404
22:37:32,451 INFO [stdout] (scheduler_Worker-9) Server returned non-OK code: 404
22:37:32,457 INFO [stdout] (scheduler_Worker-9) Server returned non-OK code: 404
22:37:32,463 INFO [stdout] (scheduler_Worker-9) Server returned non-OK code: 404
22:37:32,468 INFO [stdout] (scheduler_Worker-9) Server returned non-OK code: 404
22:37:32,476 INFO [stdout] (scheduler_Worker-9) Server returned non-OK code: 404
22:37:32,483 INFO [stdout] (scheduler_Worker-9) Server returned non-OK code: 404
22:37:32,486 INFO [stdout] (scheduler_Worker-9) 22:37:32.485 [scheduler_Worker-9] INFO o.o.s.o.OpenIoTServicesManagerImpl - Loaded 0 services.

So I get 10 non-OK codes (same number as services).
I get the same list of messages in my terminal every two minutes.

In the terminal where I executed the first 'deploy' command I get the following:
{"JBAS014671: Failed services" => {"jboss.web.deployment.default-host.\"/lsm-light.server\"" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host.\"/lsm-light.server\": JBAS018040: Failed to start context"}}
[standalone@localhost:9999 /] deploy /media/openiot/openiot-code/modules/lsm-light/lsm-light.server/target/lsm-light.server.war --force

How can I get this working? I'm not familiar with JBoss and I'm looking into this deeper.
Which links, literature or concepts I should look into to solve this?

Nick Decroos

unread,
Sep 14, 2016, 9:15:22 AM9/14/16
to OpenIoT

For clarity: I'm following the steps under 'Steps to Update and Redeploy OpenIoT with latest version in GitHub.'
I interpreted the explanation next to IMPORTANT as that I should first execute this part before I could continue with the part 'End User Manual - Steps to trial OpenIoT platform'.

Miguel Ángel Martínez Sánchez

unread,
Mar 22, 2017, 5:46:26 AM3/22/17
to OpenIoT

Did you resolve it?

G. M.

unread,
Sep 24, 2018, 6:09:35 PM9/24/18
to OpenIoT
Can someone correct this error?
Reply all
Reply to author
Forward
0 new messages