How To Solve Issues Related to Log – Failed to read file (version 6.8)

How To Solve Issues Related to Log – Failed to read file (version 6.8)

Updated: Jan-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 “Failed to read file (version 6.8)” it’s important to understand a few problems related to Elasticsearch concepts discovery, discovery-file, hosts. See bellow important tips and explanations on these concepts

Log Context

Log”Failed to read file [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     private List readFileContents(Path path) {
        try (Stream lines = Files.lines(path)) {
            return lines.filter(line -> line.startsWith("#") == false) // lines starting with `#` are comments
        } catch (IOException e) {
            logger.warn(() -> new ParameterizedMessage("failed to read file [{}]"; unicastHostsFilePath); e);
            return Collections.emptyList();


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 Elasticsearch crashes after showing t: failed to read local state , exiting

2.27 K 2

Elasticsearch Immediately Stop Afte  

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