The LDAP search request failed: 2 (Protocol Error)

By: Eugene Batogov user 07 Nov 2019 at 9:35 a.m. CST

3 Responses
Eugene Batogov gravatar
Hello after restarting the OpenDJ, I began to receive connection errors: ``` /opt/opendj/bin/ldapsearch -h localhost -p 1636 -Z -X -D 'cn=directory manager' -w 'PASS' -b o=gluu gluuGroupType=gluuManagerGroup 1.1 The LDAP search request failed: 2 (Protocol Error) Additional Information: The Directory Server is closing the connection to this client ``` Why ? But OpenDJ server started successfully: ``` [07/Nov/2019:18:27:37 +0300] category=JVM severity=NOTICE msgID=21 msg=Installation Directory: /opt/opendj [07/Nov/2019:18:27:37 +0300] category=JVM severity=NOTICE msgID=23 msg=Instance Directory: /opt/opendj [07/Nov/2019:18:27:37 +0300] category=JVM severity=NOTICE msgID=17 msg=JVM Information: 1.8.0_222-b10 by Amazon.com Inc., 64-bit architecture, 119537664 bytes heap size [07/Nov/2019:18:27:37 +0300] category=JVM severity=NOTICE msgID=18 msg=JVM Host: sso.cti.ru, running Linux 3.10.0-1062.1.2.el7.x86_64 amd64, 3973464064 bytes physical memory size, number of processors available 4 [07/Nov/2019:18:27:37 +0300] category=JVM severity=NOTICE msgID=19 msg=JVM Arguments: "-Xms128m", "-Xmx128m", "-Dorg.opends.server.scriptName=start-ds" [07/Nov/2019:18:27:38 +0300] category=BACKEND severity=NOTICE msgID=513 msg=The database backend site containing 2 entries has started [07/Nov/2019:18:27:38 +0300] category=BACKEND severity=NOTICE msgID=513 msg=The database backend metric containing 9274 entries has started [07/Nov/2019:18:27:38 +0300] category=BACKEND severity=NOTICE msgID=513 msg=The database backend userRoot containing 1295 entries has started [07/Nov/2019:18:27:38 +0300] category=EXTENSIONS severity=NOTICE msgID=221 msg=DIGEST-MD5 SASL mechanism using a server fully qualified domain name of: localhost [07/Nov/2019:18:27:38 +0300] category=CORE severity=NOTICE msgID=135 msg=The Directory Server has started successfully [07/Nov/2019:18:27:38 +0300] category=CORE severity=NOTICE msgID=139 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID org.opends.messages.core-135): The Directory Server has started successfully [07/Nov/2019:18:27:39 +0300] category=PROTOCOL severity=NOTICE msgID=276 msg=Started listening for new connections on Administration Connector localhost port 4444 [07/Nov/2019:18:27:39 +0300] category=PROTOCOL severity=NOTICE msgID=276 msg=Started listening for new connections on LDAPS Connection Handler localhost port 1636 ```
Gluu 4.0 CentOS 7.2
closed

Answers

By Aliaksandr Samuseu staff 07 Nov 2019 at 9:46 a.m. CST

Copy
Aliaksandr Samuseu gravatar
Hi, Eugene. Try to exist the container, stop it completely, and start again.

By Eugene Batogov user 07 Nov 2019 at 9:53 a.m. CST

Copy
Eugene Batogov gravatar
I don't use docker :( ``` 18:47 ==> /opt/gluu-server/opt/opendj/logs/access <== [07/Nov/2019:18:37:58 +0300] BIND REQ conn=0 op=0 msgID=1 version=3 type=SIMPLE dn="cn=directory manager" [07/Nov/2019:18:37:58 +0300] DISCONNECT conn=0 reason="Protocol Error" [07/Nov/2019:18:37:58 +0300] BIND RES conn=0 op=0 msgID=1 result=0 authDN="cn=Directory Manager,cn=Root DNs,cn=config" etime=12 ==> /opt/gluu-server/opt/opendj/logs/ldap-access.audit.json <== {"eventName":"DJ-LDAP","client":{"ip":"127.0.0.1","port":34444},"server":{"ip":"127.0.0.1","port":1636},"request":{"protocol":"LDAPS","operation":"BIND","connId":0,"msgId":1,"version":"3","authType":"Simple","dn":"cn=directory manager"},"transactionId":"0","response":{"status":"SUCCESSFUL","statusCode":"0","elapsedTime":12,"elapsedTimeUnits":"MILLISECONDS"},"userId":"cn=Directory Manager,cn=Root DNs,cn=config","timestamp":"2019-11-07T15:37:58.773Z","_id":"b9177c73-a7f2-43f6-b4f5-df346f6e0f49-3"} {"eventName":"DJ-LDAP","client":{"ip":"127.0.0.1","port":34444},"server":{"ip":"127.0.0.1","port":1636},"request":{"protocol":"LDAPS","operation":"DISCONNECT","connId":0},"transactionId":"0","response":{"status":"SUCCESSFUL","statusCode":"0","elapsedTime":0,"elapsedTimeUnits":"MILLISECONDS","reason":"Protocol Error"},"timestamp":"2019-11-07T15:37:58.780Z","_id":"b9177c73-a7f2-43f6-b4f5-df346f6e0f49-2"} ``` but opendj run under user dockerroot, but in fs file belong to user: ldap

By Aliaksandr Samuseu staff 07 Nov 2019 at 10:05 a.m. CST

Copy
Aliaksandr Samuseu gravatar
I meant you need to exit chroot environment and stop the "gluu-server" service, then start it again.

Post an answer