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

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Jan-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Cannot obtain short path for because JNA is not available” it’s important to understand common problems related to Elasticsearch concepts: bootstrap. See detailed explanations below complete with common problems, examples and useful tips.

To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

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

2To Fix An Unsatisfiedlinkerror Can  

Log Context

Log ”Cannot obtain short path for [{}] because JNA is not available” classname is
We have extracted the following from Elasticsearch source code to get 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);

About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster