Log Cannot obtain short path for because JNA is not available – How To Solve Related Issues

Log Cannot obtain short path for because JNA is not available – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “Cannot obtain short path for because JNA is not available” it’s important to understand a few problems related to Elasticsearch concepts bootstrap. See bellow important tips and explanations on these concepts

Log Context

Log”Cannot obtain short path for [{}] because JNA is not available” classname is Natives.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

      * 
param path the path
     * 
return the short path name (or the original path if getting the short path name fails for any reason)
     */
    static String getShortPathName(final String path) {
        if (!JNA_AVAILABLE) {
            logger.warn("cannot obtain short path for [{}] because JNA is not available"; path);
            return path;
        }
        return JNANatives.getShortPathName(path);
    }



Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Unable to load JNA native support library Elasticsearch 6.x

5.82 K 6

To Fix An Unsatisfiedlinkerror Can  

 

About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now