[Image] Opensearch:2.12 instantly crashing after upgrading to MacOs Sequoia 15.3 "Loading hsdis library failed"

[OliverRC]

Version of Warden

0.15.0

Operating System and Installation Method

Mac OS Sequoia 15.3

Image

wardenenv/opensearch:2.12

Describe the Bug

Everything was working fine yesterday. MacOS updated to 15.3 last night. Now opensearch image instantly crashes.
I've remove the image and pulled the latest from Docker and restarted the environment and same deal.

Crash log information:

2025-02-05 12:38:59 Disabling OpenSearch Security Plugin
2025-02-05 12:38:59 Enabling execution of OPENSEARCH_HOME/bin/opensearch-performance-analyzer/performance-analyzer-agent-cli for OpenSearch Performance Analyzer Plugin
2025-02-05 12:38:59 #
2025-02-05 12:38:59 # A fatal error has been detected by the Java Runtime Environment:
2025-02-05 12:38:59 #
2025-02-05 12:38:59 #  SIGILL (0x4) at pc=0x0000ffffa7d3fc5c, pid=35, tid=37
2025-02-05 12:38:59 #
2025-02-05 12:38:59 # JRE version:  (21.0.2+13) (build )
2025-02-05 12:38:59 # Java VM: OpenJDK 64-Bit Server VM (21.0.2+13-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
2025-02-05 12:38:59 # Problematic frame:
2025-02-05 12:38:59 # j  java.lang.System.registerNatives()V+0 [email protected]
2025-02-05 12:38:59 #
2025-02-05 12:38:59 # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
2025-02-05 12:38:59 #
2025-02-05 12:38:59 # An error report file with more information is saved as:
2025-02-05 12:38:59 # /usr/share/opensearch/hs_err_pid35.log
2025-02-05 12:38:59 [0.021s][warning][os] Loading hsdis library failed
2025-02-05 12:38:59 #
2025-02-05 12:38:59 # The crash happened outside the Java Virtual Machine in native code.
2025-02-05 12:38:59 # See problematic frame for where to report the bug.
2025-02-05 12:38:59 #
2025-02-05 12:39:22 Disabling OpenSearch Security Plugin
2025-02-05 12:39:22 Enabling execution of OPENSEARCH_HOME/bin/opensearch-performance-analyzer/performance-analyzer-agent-cli for OpenSearch Performance Analyzer Plugin
2025-02-05 12:39:22 #
2025-02-05 12:39:22 # A fatal error has been detected by the Java Runtime Environment:
2025-02-05 12:39:22 #
2025-02-05 12:39:22 #  SIGILL (0x4) at pc=0x0000ffff9bd3fc5c, pid=35, tid=37
2025-02-05 12:39:22 #
2025-02-05 12:39:22 # JRE version:  (21.0.2+13) (build )
2025-02-05 12:39:22 # Java VM: OpenJDK 64-Bit Server VM (21.0.2+13-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
2025-02-05 12:39:22 # Problematic frame:
2025-02-05 12:39:22 # j  java.lang.System.registerNatives()V+0 [email protected]
2025-02-05 12:39:22 #
2025-02-05 12:39:22 # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
2025-02-05 12:39:22 #
2025-02-05 12:39:22 # An error report file with more information is saved as:
2025-02-05 12:39:22 # /usr/share/opensearch/hs_err_pid35.log
2025-02-05 12:39:22 [0.016s][warning][os] Loading hsdis library failed
2025-02-05 12:39:22 #
2025-02-05 12:39:22 # The crash happened outside the Java Virtual Machine in native code.
2025-02-05 12:39:22 # See problematic frame for where to report the bug.
2025-02-05 12:39:22 #
2025-02-05 12:38:59 /usr/share/opensearch/bin/opensearch-env: line 99:    35 Aborted                 "$JAVA" "$XSHARE" -cp "$OPENSEARCH_CLASSPATH" org.opensearch.tools.java_version_checker.JavaVersionChecker
2025-02-05 12:39:22 /usr/share/opensearch/bin/opensearch-env: line 99:    35 Aborted                 "$JAVA" "$XSHARE" -cp "$OPENSEARCH_CLASSPATH" org.opensearch.tools.java_version_checker.JavaVersionChecker

To Reproduce

1. warden env up
2. Notice Opensearch has stopped, logs show crash information

Expected Behavior

No response

Additional context

No response

[OliverRC]

I was able to get it to start now by creating a .warden/warden-env.yml file and providing the following:

services:
  opensearch:
    environment:
      _JAVA_OPTIONS: "-XX:UseSVE=0"

I don't know what UseSVE is, but it seems to be a common issue with MacOS releases.

Edit: Seems SVE is Scalable Vector Engine. e.g Disable Scalable Vector Engine

[navarr]

Thank you for your report and investigation Oliver!

It looks like we may want to universally disable SVE in any of our Java engines, but I'm hesitant to do so

[PatrickWhitehouse]

Cheers @OliverRC - that saved me 😄