Closed siwen-yu closed 1 year ago
interesting, not only the FE component was not started, but also the broker and BE service.
Can you pull the broker log at /data/deploy/starrocks/apache_hdfs_broker/log
and be log at /data/deploy/starrocks/be/log
, check if there is more information about the crash.
interesting, not only the FE component was not started, but also the broker and BE service.
Can you pull the broker log at
/data/deploy/starrocks/apache_hdfs_broker/log
and be log at/data/deploy/starrocks/be/log
, check if there is more information about the crash.
/data/deploy/starrocks/apache_hdfs_broker/log
just like the FE component, it's the same JVM error.
/data/deploy/starrocks/be/log
did you inject a different JAVA_HOME env?
did you inject a different JAVA_HOME env?
This is the official docker image. I didn't do any changes。
can you get the starrocks/allin1-ubuntu:latest image digest (the sha256), I need to confirm the exact version of the image?
Also this log is suspecious, if with the default JAVA_HOME=/lib/jvm/default-java, the libjvm.so can be found at /lib/jvm/default-java/lib/server/libjvm.so
, shouldn't report the file not found.
can you get the starrocks/allin1-ubuntu:latest image digest (the sha256), I need to confirm the exact version of the image?
Also this log is suspecious, if with the default JAVA_HOME=/lib/jvm/default-java, the libjvm.so can be found at
/lib/jvm/default-java/lib/server/libjvm.so
, shouldn't report the file not found.
Of course, i got the sha256 from docker:
sha256:88b810a4000b56dc0e112f8f7736696cea45ec06afe30eac3f2cbaf530919164
In additiion, the /lib/jvm/default-java/lib/server/libjvm.so
can be found.
can you login to the container and collect following information
can you login to the container and collect following information
- uname -a
- ulimit -a
- env (necessary filtering or masking if there is any sensitive information)
Linux fd4029f4feec 3.10.0-1160.11.1.el7.x86_64 #1 SMP Fri Dec 18 16:34:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
real-time non-blocking time (microseconds, -R) unlimited
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 256282
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1048576
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
HOSTNAME=fd4029f4feec
JAVA_HOME=/lib/jvm/default-java
PWD=/data/deploy
HOME=/root
SR_HOME=/data/deploy/starrocks
TERM=xterm
SHLVL=1
PATH=/usr/lib/linux-tools/5.15.0-60-generic:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
_=/usr/bin/env
Interesting, is it proper to get in touch in person and have a live meeting for this?
Interesting, is it proper to get in touch in person and have a live meeting for this?
Sure, could you mind sending your WeChat or another personal contact information to my email? email: 18702515518@163.com
have a live meeting with @yusiwen123 , it appears that the failure of java start, caused by the seccomp profile enabled on the host. check the following doc:
https://docs.docker.com/engine/security/seccomp/ and https://github.com/adoptium/containers/issues/215#issuecomment-1142046045
fixed it by adding additional command line option --security-opt seccomp=unconfined
when using docker run
as suggested by docker document.
Thanks, I can now use it normally.
docker run -p 9030:9030 -p 8030:8030 -p 8040:8040 --security-opt seccomp=unconfined -itd --name quickstart starrocks/allin1-ubuntu
is still meet this err
@LinMingQiang please open a new issue and paste the logs/error messages.
Steps
docker pull starrocks/allin1-ubuntu:latest
docker run -p 19030:9030 -p 18030:8030 -p 18040:8040 -itd --name starrocks docker.io/starrocks/allin1-ubuntu:latest
mysql -P19030 -h127.0.0.1 -uroot --prompt="StarRocks > "
got docker container log:
Entered the Docker image and checked the fe.out log and Java commands, reporting insufficient memory for any operation.The following is the hs_err_pid.log file.
But the server's memory is sufficient.
Question
How should I continue to troubleshoot this issue?