Starting docker version runs into "Failed to start component" error

Problems with installing OpenKM? No problemo, the solution is closer than you think.
Forum rules
Please, before asking something see the documentation wiki or use the search feature of the forum. And remember we don't have a crystal ball or mental readers, so if you post about an issue tell us which OpenKM are you using and also the browser and operating system version. For more info read How to Report Bugs Effectively.
Post Reply
kalle42
Fresh Boarder
Fresh Boarder
Posts: 10
Joined: Mon Sep 23, 2019 3:20 pm

Starting docker version runs into "Failed to start component" error

Post by kalle42 » Mon Sep 23, 2019 3:54 pm

Hello,

I'm new to openkm. I tried to install and run the latest docker version of openkm on a win10 computer. At the first start there was an error, which I did not pay attention but tried again. This time I think it starts as it should. (I'm not able to interpret all these Infos and Warnings yet! But there was no Severe message). At this point, I had some problems to connect to virtual machine (404). I tried some IP-Addresses and read a lot to find out which the correct IP and Port combination is. I uninstalled my Virtualbox and reinstalled (removed and pulled) the container meantime, but I did not find a combination. Occasionally I could not run the container on the first attempt due to the error.

But now the error occurs on every attempt:

Code: Select all

23-Sep-2019 14:44:53.848 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.24
23-Sep-2019 14:44:53.878 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/opt/openkm/webapps/OpenKM.war]
23-Sep-2019 14:44:53.891 WARNING [localhost-startStop-1] org.apache.catalina.startup.SetContextPropertiesRule.begin [SetContextPropertiesRule]{Context} Setting property 'antiJARLocking' to 'true' did not find a matching property.
23-Sep-2019 14:44:53.893 WARNING [localhost-startStop-1] org.apache.catalina.startup.SetContextPropertiesRule.begin [SetContextPropertiesRule]{Context} Setting property 'allowLinking' to 'true' did not find a matching property.
23-Sep-2019 14:44:58.121 SEVERE [localhost-startStop-1] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start:
 org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/OpenKM]]
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: Unable to complete the scan for annotations for web application [/OpenKM] due to a StackOverflowError. Possible root causes include a too low setting for -Xss and illegal cyclic inheritance dependencies. The class hierarchy being processed was [org.bouncycastle.asn1.ASN1EncodableVector->org.bouncycastle.asn1.DEREncodableVector->org.bouncycastle.asn1.ASN1EncodableVector]
        at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:2110)
        at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2054)
        at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:2000)
        at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1970)
        at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1923)
        at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1163)
        at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:775)
        at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299)
        at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5105)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
        ... 10 more

23-Sep-2019 14:44:58.124 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive [/opt/openkm/webapps/OpenKM.war]
 java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/OpenKM]]
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:756)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

23-Sep-2019 14:44:58.129 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/opt/openkm/webapps/OpenKM.war] has finished in [4,246] ms
23-Sep-2019 14:44:58.130 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/openkm/webapps/ROOT]
23-Sep-2019 14:44:58.133 WARNING [localhost-startStop-1] org.apache.catalina.startup.SetContextPropertiesRule.begin [SetContextPropertiesRule]{Context} Setting property 'antiJARLocking' to 'true' did not find a matching property.
23-Sep-2019 14:44:58.547 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
23-Sep-2019 14:44:58.589 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/openkm/webapps/ROOT] has finished in [459] ms
23-Sep-2019 14:44:58.595 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-0.0.0.0-8080"]
23-Sep-2019 14:44:58.601 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-127.0.0.1-8009"]
23-Sep-2019 14:44:58.604 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 4797 ms
time="2019-09-23T16:51:44+02:00" level=error msg="error waiting for container: EOF"
I found some resolution trials but I think I'm not able to make changes to anything what is in the container. (I'm also new docker!)

Thank you very much for your help,
Kalle

pavila
Moderator
Moderator
Posts: 3086
Joined: Tue Dec 11, 2007 6:02 pm
Location: Alicante, Spain
Contact:

Re: Starting docker version runs into "Failed to start component" error

Post by pavila » Tue Oct 01, 2019 9:19 am

Please, tell me exactly how do you start the container. I've tried and works pretty fine.

Code: Select all

docker run -it -p 8080:8080 openkm/openkm-ce
Regards.

kalle42
Fresh Boarder
Fresh Boarder
Posts: 10
Joined: Mon Sep 23, 2019 3:20 pm

Re: Starting docker version runs into "Failed to start component" error

Post by kalle42 » Wed Oct 02, 2019 3:12 pm

Hello,

thanks for your answer.

I startet without the "-it"

Code: Select all

docker run -p 8080:8080 openkm/openkm-ce
As I mentioned, the error occurs occasionally. After stopping and running again, it mostly starts successfully.

I add the complete output of a not successful start:

Code: Select all

PS C:\Users\kwgerarts> docker run -p 8080:8080 openkm/openkm-ce
02-Oct-2019 12:26:17.151 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version:        Apache Tomcat/8.5.24
02-Oct-2019 12:26:17.156 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Nov 27 2017 13:05:30 UTC
02-Oct-2019 12:26:17.156 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number:         8.5.24.0
02-Oct-2019 12:26:17.156 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Linux
02-Oct-2019 12:26:17.157 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            4.9.184-linuxkit
02-Oct-2019 12:26:17.157 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
02-Oct-2019 12:26:17.157 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             /usr/lib/jvm/java-8-oracle/jre
02-Oct-2019 12:26:17.157 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           1.8.0_201-b09
02-Oct-2019 12:26:17.157 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Oracle Corporation
02-Oct-2019 12:26:17.157 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         /opt/openkm
02-Oct-2019 12:26:17.157 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         /opt/openkm
02-Oct-2019 12:26:17.157 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/opt/openkm/conf/logging.properties
02-Oct-2019 12:26:17.158 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
02-Oct-2019 12:26:17.158 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms256m
02-Oct-2019 12:26:17.158 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx2048m
02-Oct-2019 12:26:17.158 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseG1GC
02-Oct-2019 12:26:17.158 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
02-Oct-2019 12:26:17.158 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.net.preferIPv4Stack=true
02-Oct-2019 12:26:17.158 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dfile.encoding=UTF-8
02-Oct-2019 12:26:17.158 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dsun.jnu.encoding=UTF-8
02-Oct-2019 12:26:17.158 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.ignoreunknownencoding=true
02-Oct-2019 12:26:17.158 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
02-Oct-2019 12:26:17.159 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
02-Oct-2019 12:26:17.159 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=
02-Oct-2019 12:26:17.159 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/opt/openkm
02-Oct-2019 12:26:17.159 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/opt/openkm
02-Oct-2019 12:26:17.159 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/opt/openkm/temp
02-Oct-2019 12:26:17.159 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [:/opt/openkm/lib/sigar:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib]
02-Oct-2019 12:26:17.377 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-0.0.0.0-8080"]
02-Oct-2019 12:26:17.395 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
02-Oct-2019 12:26:17.412 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-127.0.0.1-8009"]
02-Oct-2019 12:26:17.450 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
02-Oct-2019 12:26:17.451 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 858 ms
02-Oct-2019 12:26:17.503 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
02-Oct-2019 12:26:17.503 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.24
02-Oct-2019 12:26:17.546 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/opt/openkm/webapps/OpenKM.war]
02-Oct-2019 12:26:17.566 WARNING [localhost-startStop-1] org.apache.catalina.startup.SetContextPropertiesRule.begin [SetContextPropertiesRule]{Context} Setting property 'antiJARLocking' to 'true' did not find a matching property.
02-Oct-2019 12:26:17.572 WARNING [localhost-startStop-1] org.apache.catalina.startup.SetContextPropertiesRule.begin [SetContextPropertiesRule]{Context} Setting property 'allowLinking' to 'true' did not find a matching property.
02-Oct-2019 12:26:23.264 SEVERE [localhost-startStop-1] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start:
 org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/OpenKM]]
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: Unable to complete the scan for annotations for web application [/OpenKM] due to a StackOverflowError. Possible root causes include a too low setting for -Xss and illegal cyclic inheritance dependencies. The class hierarchy being processed was [org.bouncycastle.asn1.ASN1EncodableVector->org.bouncycastle.asn1.DEREncodableVector->org.bouncycastle.asn1.ASN1EncodableVector]
        at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:2110)
        at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2054)
        at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:2000)
        at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1970)
        at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1923)
        at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1163)
        at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:775)
        at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299)
        at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5105)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
        ... 10 more

02-Oct-2019 12:26:23.268 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive [/opt/openkm/webapps/OpenKM.war]
 java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/OpenKM]]
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:756)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

02-Oct-2019 12:26:23.271 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/opt/openkm/webapps/OpenKM.war] has finished in [5,723] ms
02-Oct-2019 12:26:23.273 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/openkm/webapps/ROOT]
02-Oct-2019 12:26:23.278 WARNING [localhost-startStop-1] org.apache.catalina.startup.SetContextPropertiesRule.begin [SetContextPropertiesRule]{Context} Setting property 'antiJARLocking' to 'true' did not find a matching property.
02-Oct-2019 12:26:23.759 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
02-Oct-2019 12:26:23.801 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/openkm/webapps/ROOT] has finished in [528] ms
02-Oct-2019 12:26:23.807 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-0.0.0.0-8080"]
02-Oct-2019 12:26:23.822 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-127.0.0.1-8009"]

pavila
Moderator
Moderator
Posts: 3086
Joined: Tue Dec 11, 2007 6:02 pm
Location: Alicante, Spain
Contact:

Re: Starting docker version runs into "Failed to start component" error

Post by pavila » Thu Oct 03, 2019 7:22 am

Unable to reproduce, but it seems a problem related to low memory. How much RAM do you have?

Regards.

kalle42
Fresh Boarder
Fresh Boarder
Posts: 10
Joined: Mon Sep 23, 2019 3:20 pm

Re: Starting docker version runs into "Failed to start component" error

Post by kalle42 » Fri Oct 04, 2019 7:35 am

Hello,

I got 16 GB ram.

But I found s.th. else here. Could that not point to a similar problem?
jllort wrote:
Wed Sep 04, 2019 9:54 pm

Anyway is quite strange you are getting an stack error:

Code: Select all

Unable to complete the scan for annotations for web application [/OpenKM] due to a StackOverflowError
In past we found some error with org.bouncycastle ( this is a tedious issue because when happens it depends on jar class loading ordering and happens randomly what makes resolution more hard ).

Code: Select all

The class hierarchy being processed was [org.bouncycastle.asn1.ASN1EncodableVector->org.bouncycastle.asn1.DEREncodableVector->org.bouncycastle.asn1.ASN1EncodableVector]
Thank you.

Regards,
Kalle

pavila
Moderator
Moderator
Posts: 3086
Joined: Tue Dec 11, 2007 6:02 pm
Location: Alicante, Spain
Contact:

Re: Starting docker version runs into "Failed to start component" error

Post by pavila » Fri Oct 04, 2019 7:54 am

I don't know why it's working every time I tried in my computer and always fails in yours.

kalle42
Fresh Boarder
Fresh Boarder
Posts: 10
Joined: Mon Sep 23, 2019 3:20 pm

Re: Starting docker version runs into "Failed to start component" error

Post by kalle42 » Fri Oct 04, 2019 8:02 am

It does not always fail! It fails from time to time. After starting maximum three or four times I have a correct start. But often it runs with first try.

pavila
Moderator
Moderator
Posts: 3086
Joined: Tue Dec 11, 2007 6:02 pm
Location: Alicante, Spain
Contact:

Re: Starting docker version runs into "Failed to start component" error

Post by pavila » Fri Oct 04, 2019 10:02 am

I've updated the Docker image with the latest OpenKM release. Please, try again and tell me if this fix the issue.

Regards.

kalle42
Fresh Boarder
Fresh Boarder
Posts: 10
Joined: Mon Sep 23, 2019 3:20 pm

Re: Starting docker version runs into "Failed to start component" error

Post by kalle42 » Fri Oct 04, 2019 1:09 pm

Hello,

thank you for your help.

I pulled again the latest image of openkm/openkm-ce.
I ran the image and stopped the container several times without any severe error messages. Your fix seems to work on my computer.
Anyway I will not run docker images so often in future. But that's another thread ...

By the way, I noticed that the latest (6.3.8 ) Version is more than 300 MB smaller than the previous ones. Was that intended?

Regards,
Kalle

tcconsulting
Fresh Boarder
Fresh Boarder
Posts: 7
Joined: Fri Jun 02, 2017 6:50 pm

Re: Starting docker version runs into "Failed to start component" error

Post by tcconsulting » Tue Oct 08, 2019 8:50 pm

I was having the same issue and this new release seems to have fixed it. We had been able to run this container in Docker on an Azure Linux VM just six weeks ago, but when we tried it last week we got the StackOverflow error.

We still don't know why it stopped working for us and are interested in the changes to 6.3.8 that might have fixed the problem.

tcconsulting
Fresh Boarder
Fresh Boarder
Posts: 7
Joined: Fri Jun 02, 2017 6:50 pm

Re: Starting docker version runs into "Failed to start component" error

Post by tcconsulting » Wed Oct 09, 2019 2:57 pm

Unfortunately, it hasn't fixed it. I'm able to run OpenKM to create a new database, but running it with the database already created throws the stack overflow error.

pavila
Moderator
Moderator
Posts: 3086
Joined: Tue Dec 11, 2007 6:02 pm
Location: Alicante, Spain
Contact:

Re: Starting docker version runs into "Failed to start component" error

Post by pavila » Fri Oct 18, 2019 3:30 pm

Try with this new image from OpenKM v6.3.9-DEV

Code: Select all

docker run -it -p 8080:8080 openkm/openkm-ce:6.3.9-DEV

Post Reply