Briefly, this error occurs when there is a misconfiguration in the Elasticsearch security settings. It seems like there is a contradiction in the settings, as it’s stating that security is both enabled and disabled. To resolve this issue, you should check your Elasticsearch configuration file (elasticsearch.yml) and ensure that the security settings are correctly set. If you want to enable security, set ‘xpack.security.enabled: true’. If you want to disable it, set ‘xpack.security.enabled: false’. Make sure there are no duplicate entries contradicting each other.
This guide will help you check for common problems that cause the log ” Security is {}”; enabled ? “enabled” : “disabled ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “Security is {}”; enabled ? “enabled” : “disabled” classname is Security.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
NamedXContentRegistry xContentRegistry;
Environment environment;
NodeMetadata nodeMetadata;
IndexNameExpressionResolver expressionResolver
) throws Exception {
logger.info("Security is {}"; enabled ? "enabled" : "disabled");
if (enabled == false) {
return Collections.singletonList(new SecurityUsageServices(null; null; null; null; null; null));
}
systemIndices.init(client; clusterService);
