Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make yamcs-up is returning A fatal error has been detected by the Java Runtime Environment: #43

Open
haisamido opened this issue Sep 19, 2024 · 5 comments

Comments

@haisamido
Copy link
Contributor

cd ./docker && make yamcs-up

is returning the below error:

Downloaded from central: https://repo.maven.apache.org/maven2/com/github/luben/zstd-jni/1.5.5-11/zstd-jni-1.5.5-11.jar (6.8 MB at 11 MB/s)
[INFO] 
[INFO] <<< yamcs:1.3.2:run (default-cli) < process-classes @ myproject <<<
[INFO] 
[INFO] 
[INFO] --- yamcs:1.3.2:run (default-cli) @ myproject ---
[INFO] Creating configuration at /yamcs/target/yamcs
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGILL (0x4) at pc=0x00007fffba6aa68f, pid=117, tid=121
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.12+7 (17.0.12+7) (build 17.0.12+7)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.12+7 (17.0.12+7, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  [librocksdbjni4105156113712216977.so+0x33968f]
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /yamcs/target/yamcs/hs_err_pid117.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  17.422 s
[INFO] Finished at: 2024-09-19T21:43:23Z
[INFO] ------------------------------------------------------------------------
 *  Terminal will be reused by tasks, press any key to close it. 
@xpromache
Copy link
Member

Sorry for that, see here how to solve it:
yamcs/yamcs#937

Which CPU are you using?

I will make the default Rocksdb compatible with older CPUs, I'm just not sure yet how old.

@haisamido
Copy link
Contributor Author

Sorry for that, see here how to solve it: yamcs/yamcs#937

Which CPU are you using?

I will make the default Rocksdb compatible with older CPUs, I'm just not sure yet how old.

I am using a Macbook Pro M2 Laptop https://en.wikipedia.org/wiki/Apple_M2

@xpromache
Copy link
Member

From this line:

Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.12+7 (17.0.12+7, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)

looks like it is linux am64 not a Mac M2 ARM CPU.

@haisamido
Copy link
Contributor Author

haisamido commented Sep 23, 2024

@xpromache when will the librocksdbjni4105156113712216977.so+0x33968f issue be resolved. @ShaneCray

@xpromache
Copy link
Member

I pushed on master a change to use a rocksdb library compatible to CPUs as old as Intel core 2.
It will be part of the next release, not sure when that will be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants