architolk / Linked-Data-Theatre

The Linked Data Theatre is a platform for an optimal presentation of Linked Data
GNU General Public License v3.0
38 stars 21 forks source link

Virtuoso does not startup in docker (windows) #60

Open lkoning opened 7 years ago

lkoning commented 7 years ago

see log below. Somethings wrong with the Virtuoso buildscript.

Creating ldt ... Creating virtuoso ... Creating virtuoso Creating virtuoso ... done Attaching to ldt, virtuoso virtuoso | standard_init_linux.go:187: exec user process caused "no such file or directory" ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: Server version: Apache Tomcat/7.0.79 ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: Server built: Jun 26 2017 16:25:20 UTC ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: Server number: 7.0.79.0 ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: OS Name: Linux ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: OS Version: 4.9.31-moby ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: Architecture: amd64 ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: Java Home: /usr/lib/jvm/java-8-openjdk-amd64/jre ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: JVM Version: 1.8.0_131-8u131-b11-1~bpo8+1-b11 ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: JVM Vendor: Oracle Corporation ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: CATALINA_BASE: /usr/local/tomcat ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: CATALINA_HOME: /usr/local/tomcat ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: Command line argument: -Djava.util.logging.config.file=/usr/local/tomcat/conf/logging.properties ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: Command line argument: -Djdk.tls.ephemeralDHKeySize=2048 ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: Command line argument: -Djava.endorsed.dirs=/usr/local/tomcat/endorsed ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: Command line argument: -Dcatalina.base=/usr/local/tomcat ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: Command line argument: -Dcatalina.home=/usr/local/tomcat ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.startup.VersionLoggerListener log ldt | INFO: Command line argument: -Djava.io.tmpdir=/usr/local/tomcat/temp ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent ldt | INFO: Loaded APR based Apache Tomcat Native library 1.2.12 using APR version 1.5.1. ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent ldt | INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. ldt | Jul 10, 2017 9:58:10 AM org.apache.catalina.core.AprLifecycleListener initializeSSL ldt | INFO: OpenSSL successfully initialized (OpenSSL 1.1.0f 25 May 2017) ldt | Jul 10, 2017 9:58:11 AM org.apache.coyote.AbstractProtocol init ldt | INFO: Initializing ProtocolHandler ["http-apr-8080"] ldt | Jul 10, 2017 9:58:11 AM org.apache.coyote.AbstractProtocol init ldt | INFO: Initializing ProtocolHandler ["ajp-apr-8009"] ldt | Jul 10, 2017 9:58:11 AM org.apache.catalina.startup.Catalina load ldt | INFO: Initialization processed in 991 ms virtuoso exited with code 1 ldt | Jul 10, 2017 9:58:11 AM org.apache.catalina.core.StandardService startInternal ldt | INFO: Starting service Catalina ldt | Jul 10, 2017 9:58:11 AM org.apache.catalina.core.StandardEngine startInternal ldt | INFO: Starting Servlet Engine: Apache Tomcat/7.0.79 ldt | Jul 10, 2017 9:58:11 AM org.apache.coyote.AbstractProtocol start ldt | INFO: Starting ProtocolHandler ["http-apr-8080"] ldt | Jul 10, 2017 9:58:11 AM org.apache.coyote.AbstractProtocol start ldt | INFO: Starting ProtocolHandler ["ajp-apr-8009"] ldt | Jul 10, 2017 9:58:11 AM org.apache.catalina.startup.Catalina start ldt | INFO: Server startup in 113 ms

TallTed commented 6 years ago

@lkoning Were you able to resolve this? If not, and still interested, it's worth checking the virtuoso.log and system error logs to see if there's any more specific information about what specific file is missing.

ifourvimal commented 6 years ago

Where do I locate the virtuoso.log file on windows?

TallTed commented 6 years ago

@ifourvimal - We force very little, including the location (and even filename) of the virtuoso.log. In a default deployment, the instance configuration file (virtuoso.ini), database file (virtuoso.db), and log file (virtuoso.log) are found in the same directory, which is typically the database directory alongside the bin directory. The easiest way to locate these is with the Windows Explorer search utility (which will also show you if there are multiple files by the same name).

ifourvimal commented 6 years ago

Hi @TallTed Thanks for the reply I have followed your instruction and try to find the configuration file (virtuoso.ini), database file (virtuoso.db), and log file (virtuoso.log) in the Link Data Theater project as you mention using the "Windows explorer search utility" but I didn't find the any of the files. Also, There are two folders 1) virtuoso which having two files one is dockerfile and other is run.sh 2) virtuoso_data folder is blank.Is there any configuration I need to do in docker-compose.yml.Thanks for your help and time.

lkoning commented 6 years ago

hi, I stopped working with LDT so don't really remember how I fixed it. It had something to do with doing things in the right order. And maybe some permissions in linux. Your best bet is doing all the steps from the builld scripts manually.

TallTed commented 6 years ago

@ifourvimal - I'm sorry; it sounds like the issue really does lie within LDT, as Virtuoso isn't there yet. I have no direct involvement with LDT. We have to hope that @architolk returns to activity here.

architolk commented 6 years ago

The dockerfiles (and most of the Linux stuff) are created by somebody else, I'm not really familiar with the way that the docker environment is set-up. I will contact the guy that made these.