legacy-knowledge-base
公開されました Jun. 30, 2025

Elasticsearch is not starting up receiving NoNodeAvailableException and JNA native support exception

written-by

Anushka Tiwari

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

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

legacy-article

learn-legacy-article-disclaimer-text

Issue

  • Elasticsearch is not running properly, receiving the below errors:
    ERROR [liferay/search_writer/SYSTEM_ENGINE-371][ElasticsearchIndexWriter:143] java.lang.RuntimeException: org.elasticsearch.client.transport.NoNodeAvailableException:
    NoNodeAvailableException[None of the configured nodes are available.
    [WARN ][o.e.b.Natives ] [node-1] unable to load JNA native support library, native methods will be disabled.

    java.lang.UnsatisfiedLinkError: /tmp/elasticsearch.LhNfdE3i/jna--1985354563/jna2430506984811668592.tmp: /tmp/elasticsearch.LhNfdE3i/jna--1985354563/jn

Environment

  • Liferay DXP 7.2

Resolution

  • If it is a single-node elasticsearch cluster then try to add the discovery.type: single-node in the elasticsearch.yml.

  • The discovery.type: specifies whether Elasticsearch should form a multiple-node cluster.
           1. Defaults to multi-node, which means that Elasticsearch discovers other nodes when                       forming a cluster and allows other nodes to join the cluster later.
           2. If set to single-node, Elasticsearch forms a single-node cluster. When this setting is                         enabled, a node will elect itself as the master and will not join a cluster with other nodes
  • After adding the above property, try to restart the server after clearing the temporary directories, as mentioned below:
    a. Delete {Liferay_Home}/osgi/state folder
    c. Delete{Liferay_Home}/work
    d. Delete{Tomcat_Home}/temp and {Tomcat_Home}/work
    e. Restart the server

Additional Information

did-this-article-resolve-your-issue

legacy-knowledge-base