Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.
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.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
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 FileUserPasswdStore.java. 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) {
listeners.add(listener);
