Failed to get short path name – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to retrieve the short path name for a file or directory. This is often due to incorrect permissions or a non-existent path. To resolve this issue, you can verify the path exists and Elasticsearch has the necessary permissions to access it. Alternatively, you can try running Elasticsearch as an administrator or disabling the short path name feature if it’s not required.

This guide will help you check for common problems that cause the log ” failed to get short path name: {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: bootstrap.

Log Context

Log “failed to get short path name: {}” classname is JNANatives.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        try {
            final WString longPath = new WString("\\?\" + path);
            // first we get the length of the buffer needed
            final int length = JNAKernel32Library.getInstance().GetShortPathNameW(longPath; null; 0);
            if (length == 0) {
                logger.warn("failed to get short path name: {}"; Native.getLastError());
                return path;
            }
            final char[] shortPath = new char[length];
            // knowing the length of the buffer; now we get the short name
            if (JNAKernel32Library.getInstance().GetShortPathNameW(longPath; shortPath; length) > 0) {

 

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?