Briefly, this error occurs when Elasticsearch is configured to use operator privileges, but the operator user file is not found. This could be due to incorrect file path or the file being deleted. To resolve this, ensure the operator user file is in the correct location and the path in the configuration is correct. If the file is missing, recreate it with the necessary user details. Also, check the file permissions to ensure Elasticsearch can access it. If operator privileges are not needed, disable them in the configuration to avoid this error.
This guide will help you check for common problems that cause the log ” Operator privileges [{}] is enabled; but operator user file does not exist. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “Operator privileges [{}] is enabled; but operator user file does not exist. ” classname is FileOperatorUsersStore.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
}
public static OperatorUsersDescriptor parseFile(Path file; Logger logger) {
if (false == Files.exists(file)) {
logger.warn("Operator privileges [{}] is enabled; but operator user file does not exist. " +
"No user will be able to perform operator-only actions."; OPERATOR_PRIVILEGES_ENABLED.getKey());
return EMPTY_OPERATOR_USERS_DESCRIPTOR;
} else {
logger.debug("Reading operator users file [{}]"; file.toAbsolutePath());
try (InputStream in = Files.newInputStream(file; StandardOpenOption.READ)) {
[ratemypost]
