And } have not been specified or are not valid distinguished names; – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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)));
                }
            }




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content