Briefly, this error occurs when the distinguished names (DNs) in the Elasticsearch configuration are either not specified or are invalid. DNs are used in LDAP and SSL configurations to uniquely identify an entity. To resolve this issue, you should first verify that the DNs are correctly specified in your configuration. If they are, ensure that they are valid and correctly formatted. If you’re using SSL, check your certificate for any errors. Lastly, ensure that the Elasticsearch server can correctly resolve and reach the specified DNs.
This guide will help you check for common problems that cause the log ” [{}] and [{}} have not been specified or are not valid distinguished names; ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “[{}] and [{}} have not been specified or are not valid distinguished names;” classname is PoolingSessionFactory.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
LDAPConnectionPoolHealthCheck healthCheck = new GetEntryLDAPConnectionPoolHealthCheck(entryDn; timeout.millis();
false; false; false; true; false);
pool.setHealthCheck(healthCheck);
pool.setHealthCheckIntervalMillis(healthCheckInterval);
} else {
logger.warn(new ParameterizedMessage("[{}] and [{}} have not been specified or are not valid distinguished names;" +
"so connection health checking is disabled"; RealmSettings.getFullSettingKey(config;
PoolingSessionFactorySettings.BIND_DN);
RealmSettings.getFullSettingKey(config; PoolingSessionFactorySettings.HEALTH_CHECK_DN)));
}
}
