Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Elasticsearch fails to start with jna tmp dir configured (core dump)

Written By

Jorge García Jiménez

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • Trying to start remote Elasticsearch crashes with a core dump. 
    # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x00007f424226f40a, pid=28216, tid=139922878629632
  #
  # JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build 1.7.0_75-b13)
  # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode linux-amd64 compressed oops)
  # Problematic frame:
  # C  [jna4948368637624641726.tmp+0x1240a]  ffi_prep_closure_loc+0x1a
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.sun.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #

  ---------------  T H R E A D  ---------------

  Current thread (0x00007f424c00a000):  JavaThread "main" [_thread_in_native, id=28218, stack(0x00007f42556a0000,0x00007f42557a1000)]

  siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000000000000000

Environment

  • Elasticsearch 2.2, 5, 6.
  • Liferay DXP 7.0, 7.1 and 7.2.

Resolution

  • The system user with which Elasticsearch was running does not have an existing home directory. Once this directory is created the service will start as expected.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?