Could not read users file ” + path.toAbsolutePath() + ” – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” could not read users file ” + path.toAbsolutePath() + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “could not read users file [” + path.toAbsolutePath() + “]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

List lines;
 try {
 lines = Files.readAllLines(path; StandardCharsets.UTF_8);
 } catch (IOException ioe) {
 throw new ElasticsearchException("could not read users file [" + path.toAbsolutePath() + "]"; ioe);
 Map> userToRoles = new HashMap<>(); 
 int lineNr = 0;


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content