typedb: Unable to start Storage when starting Grakn Docker
Description
Started Grakn docker container and get the below error in the docker console:
Version: 1.5.7
Starting Storage......FAILED!
Unable to start Storage.
This is intermittent, does happen all the time. Is this resolved in the later versions? For now, I would like to continue to use 1.5.7.
Environment
- OS (where Grakn server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
- Grakn version (and platform): 1.5.7 or 1.6.2
- Grakn client: n/a
- Other environment details: Docker container: version 19.03.5 JDK used: GraalVM CE 19.2.1 (I also run it under OpenJDK8 at times)
Some more config related details: JAVA_HOME=/usr/local/graalvm-ce-19.2.1 openjdk version “1.8.0_232” OpenJDK Runtime Environment (build 1.8.0_232-20191008104205.buildslave.jdk8u-src-tar–b07) OpenJDK 64-Bit GraalVM CE 19.2.1 (build 25.232-b07-jvmci-19.2-b03, mixed mode) STORAGE_JAVAOPTS=-XX:+UseJVMCINativeLibrary -XX:+UseJVMCINativeLibrary SERVER_JAVAOPTS=-XX:+UseJVMCINativeLibrary -XX:+UseJVMCINativeLibrary GRAKN_DAEMON_JAVAOPTS=-XX:+UseJVMCINativeLibrary -XX:+UseJVMCINativeLibrary
Note: please don’t get confused by JDK8 strings above, GraalVM is based on JDK8.
Reproducible Steps
Usual grakn start server command inside a container, please try using this.
Use the command:
$ GRAKN_VERSION=1.6.2 ./grakn-runner.sh --runContainer
or
$ GRAKN_VERSION=1.6.2 ./grakn-runner.sh --jdk GRAALVM --runContainer
to see it try to start the Grakn 1.6.2 inside the container. As I said it’s intermittent and might be free space related.
Will report with the relevant logs when it happens again.
Expected Output
An up and running Grakn server
Actual Output
See in description above.
Additional information
At the time of the reporting, I didn’t have the log files as it was a closed and deleted container but have since then made changes to the script to mount a volume outside the container to generate the log files, see issue.
On the back of the slack channel discussions
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 2
- Comments: 20 (4 by maintainers)
Hi, any news, progress on that? Thanks
Is it possible to have an explanation about the closing of this issue?
A lot of OpenCTI users are encountered the same issue. I was able to reproduce by using Docker in the latest Ubuntu 19.10 on a SATA disk using volumes for persistence.
Hello,
Just a linked problem to that is when the container starts and log:
The container never stops! The expected behavior is that the container stops and tries to restart. But it is stuck indefinitely.
Apologies, it was accidental! This is definitely a concern!
Another hint: Starting Grakn Docker with a volume for persistence on a SATA disk will lead to this problem after restart (first run is ok, second one is broken).