Failed to start watching users file – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch fails to monitor changes in the users file, which is crucial for security configurations. This could be due to incorrect file permissions, file path issues, or the file being inaccessible. To resolve this, ensure the file exists at the specified location and Elasticsearch has the necessary permissions to access it. Also, check the file path in your configuration. If the issue persists, consider checking for underlying system issues like disk space or network connectivity.

This guide will help you check for common problems that cause the log ” failed to start watching users file [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “failed to start watching users file [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 FileWatcher watcher = new FileWatcher(file.getParent());
 watcher.addListener(new FileReloadListener(file; this::tryReload));
 try {
 watcherService.add(watcher; ResourceWatcherService.Frequency.HIGH);
 } catch (IOException e) {
 throw new ElasticsearchException("failed to start watching users file [{}]"; e; file.toAbsolutePath());
 }  public void addListener(Runnable listener) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?