Cannot getrlimit RLIMITFSIZE because JNA is not available – How to solve related issues

Average Read Time

2 Mins

Cannot getrlimit RLIMITFSIZE because JNA is not available – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Cannot getrlimit RLIMIT_FSIZE because JNA is not available” classname is Natives.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         JNANatives.trySetMaxSizeVirtualMemory();
    }

    static void trySetMaxFileSize() {
        if (!JNA_AVAILABLE) {
            logger.warn("cannot getrlimit RLIMIT_FSIZE because JNA is not available");
            return;
        }
        JNANatives.trySetMaxFileSize();
    }





 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content