Cannot virtual lock because JNA is not available – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-2.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch is unable to access the Java Native Access (JNA) library, which is required for certain operations like virtual memory locking. This could be due to missing or incorrectly installed JNA. To resolve this issue, ensure that the JNA library is properly installed and accessible by OpenSearch. If it’s already installed, check the library’s permissions and path configuration. Alternatively, you can disable memory locking in OpenSearch settings, but this could potentially degrade performance.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” cannot virtual lock because JNA is not available ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: bootstrap.

Log Context

Log “cannot virtual lock because JNA is not available” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :

        return JNANatives.definitelyRunningAsRoot();

    static void tryVirtualLock() {
        if (!JNA_AVAILABLE) {
            logger.warn("cannot virtual lock because JNA is not available");


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Get expert answers on Elasticsearch/OpenSearch