Hi,
We are working with a vendor of a hosted application, and we are using openldap-2.2.13-12.el4 for authentication. We are not able to login to the hosted application. This is what the vendor is getting for error message:
message] [09-14-2010T10:27:30] Attempting to bind to xx.xxx.xxx.xxxx:389 [message] [09-14-2010T10:27:30] Binding as 'uid=pperson,ou=People,dc=college,dc=edu' [message] [09-14-2010T10:27:31] Bind successful [system ] [09-14-2010T10:27:31] Checking R25 WS user [message] [09-14-2010T10:27:31] Executing query (&(objectClass=user)(sAMAccountName=test)) [message] [09-14-2010T10:27:31] Building field mappings for query (&(objectClass=user)(sAMAccountName=test)) [message] [09-14-2010T10:27:31] Search path: OU=Group,DC=college,DC=edu [error ] [09-14-2010T10:27:32] Search error: [10061] Connection refused [message] [09-14-2010T10:27:32] Search path: OU=People,DC=college,DC=edu [error ] [09-14-2010T10:27:33] Search error: [10061] Connection refused [message] [09-14-2010T10:27:33] Search path: OU=Users,DC=college,DC=edu [error ] [09-14-2010T10:27:34] Search error: [10061] Connection refused [error ] [09-14-2010T10:27:34] Query (&(objectClass=user)(sAMAccountName=test)) returned no results
We have log level 64 enabled, if we increase log level it slows the machine.
This what We are getting in the log:
Sep 16 09:31:01 ldap1 last message repeated 8 times Sep 16 09:32:06 ldap1 last message repeated 2 times Sep 16 09:33:07 ldap1 slapd[3288]: <= bdb_equality_candidates: (uniqueMember) index_param failed (18) Sep 16 09:34:26 ldap1 last message repeated 4 times Sep 16 09:35:36 ldap1 last message repeated 4 times Sep 16 09:36:39 ldap1 last message repeated 4 times Sep 16 09:37:14 ldap1 last message repeated 4 times Sep 16 09:37:23 ldap1 slapd[3288]: connection_read(26): no connection! Sep 16 09:37:26 ldap1 slapd[3288]: <= bdb_equality_candidates: (uniqueMember) index_param failed (18) Sep 16 09:38:15 ldap1 last message repeated 2 times Sep 16 09:39:16 ldap1 last message repeated 5 times Sep 16 09:40:28 ldap1 last message repeated 3 times Sep 16 09:40:56 ldap1 last message repeated 5 times Sep 16 09:41:10 ldap1 slapd[3288]: connection_read(34): no connection! Sep 16 09:41:17 ldap1 slapd[3288]: <= bdb_equality_candidates: (uniqueMember) index_param failed (18)
I have a test server I can use to troubleshoot this problem if I know what log level should I use?
Thanks,
Aziz
--On Thursday, September 16, 2010 10:22 AM -0400 "Darouichi, Aziz" adarouic@post03.curry.edu wrote:
Hi,
We are working with a vendor of a hosted application, and we are using openldap-2.2.13-12.el4 for authentication. We are not able to login to the hosted application. This is what the vendor is getting for error message:
I would note that OpenLDAP 2.2 is a historic release, and that particular version of OpenLDAP had numerous, extremely serious, bugs in it. The current stable release is 2.4.23.
Sep 16 09:41:17 ldap1 slapd[3288]: <= bdb_equality_candidates: (uniqueMember) index_param failed (18)
This error does not look related to your issue, but it would indicate that something is doing a search on uniqueMember where the filter type does not match your indexing.
I would suggest examining the logs at loglevel 256.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
We are in the process of upgrading. I just built a new RHEL 5 with 2.4.23. and we need to complete a single sign on portal project to get all applications in line to use LDAP. Its time consuming when you have to work a variety of vendors and platforms....!!!
Thanks again I was able to resolve my issue with this application.
-----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Thursday, September 16, 2010 12:18 PM To: Darouichi, Aziz; openldap-technical@openldap.org Subject: Re: Loglevel for authentication problem
--On Thursday, September 16, 2010 10:22 AM -0400 "Darouichi, Aziz" adarouic@post03.curry.edu wrote:
Hi,
We are working with a vendor of a hosted application, and we are using openldap-2.2.13-12.el4 for authentication. We are not able to login to the hosted application. This is what the vendor is getting for error message:
I would note that OpenLDAP 2.2 is a historic release, and that particular version of OpenLDAP had numerous, extremely serious, bugs in it. The current stable release is 2.4.23.
Sep 16 09:41:17 ldap1 slapd[3288]: <= bdb_equality_candidates: (uniqueMember) index_param failed (18)
This error does not look related to your issue, but it would indicate that something is doing a search on uniqueMember where the filter type does not match your indexing.
I would suggest examining the logs at loglevel 256.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-technical@openldap.org
-
Darouichi, Aziz -
Quanah Gibson-Mount