Failed to get short path name: – How to solve related issues

Average Read Time

2 Mins

Failed to get short path name: – 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 ” Failed to get short path name: ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: bootstrap.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

{{mpg_logstarted}}

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) {




 

Run the Check-Up to get a customized report like this:

Analyze your cluster