How To Solve Issues Related to Log – Failed to get short path name:

Get an Elasticsearch Check-Up

Check if your ES issues are caused from misconfigured settings
(Free 2 min process)

Check-Up

Last update: Jan-20

Elasticsearch Error Guide In Page Navigation (click to jump) :

Troubleshooting Background – start here to get the full picture       
Related Issues – selected resources on related issues  
Log Context – usefull for experts
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check Your Elasticsearch Settings for Painfull Mistakes 


Troubleshooting background

To troubleshoot Elasticsearch log “Failed to get short path name:” it’s important to know common problems related to Elasticsearch concepts: bootstrap. See below-detailed explanations 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 :

Able To Construct Api Node Object F
stackoverflow.com/questions/32882348/unable-to-construct-api-node-object-for-kubelet-failed-to-get-external-id-from

 

Unable To Start Elasticsearch 6 2 0
discuss.elastic.co/t/unable-to-start-elasticsearch-6-2-0-in-windows-10/118851

 


Log Context

Log ”Failed to get short path name:” classname is JNANatives.java
We have extracted the following from Elasticsearch source code to get 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) {






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

We are constantly updating our analysis of Elasticsearch logs, errors, and exceptions. Sharing best practices and providing troubleshooting guides.

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

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?