How To Solve Issues Related to Log – The specified location doesnt start with any

How To Solve Issues Related to Log – The specified location doesnt start with any

Updated: Feb-20

Elasticsearch Version: 1.7-8.0


Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.

To troubleshoot log “The specified location doesnt start with any” it’s important to understand a few problems related to Elasticsearch concepts repositories, repository-azure. See bellow important tips and explanations on these concepts

Log Context

Log”The specified location [{}] doesn’t start with any” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             throw new RepositoryException(; "missing location");
        Path locationFile = environment.resolveRepoFile(location);
        if (locationFile == null) {
            if (environment.repoFiles().length > 0) {
                logger.warn("The specified location [{}] doesn't start with any "
                    + "repository paths specified by the path.repo setting: [{}] "; location; environment.repoFiles());
                throw new RepositoryException(; "location [" + location
                    + "] doesn't match any of the locations specified by path.repo");
            } else {
                logger.warn("The specified location [{}] should start with a repository path specified by"

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 Location Doesnt Match Any Of The Lo  

Impossible To Create Repository For  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now