A few things to mention which may be helpful or help narrow down a root cause. . .
FIRST
I wanted to point out that I noticed you were running slapd -d -1
which just means run slapd
with debug and loggging level 1
meaning verbose
/enable all debugging
.
From what I read in the below post URL resource, if you do not run in the slapd -f <filename>
syntax and fully qualify the <filename>
to point to an "alternative" slapd.config
file, then. . . "The default is normally /usr/local/etc/openldap/slapd.conf."
Therefore, this may not actually run slapd
and point it to the configuration file to pick up the pointers/parameters you put in the alternative config file so give that a try first in case this is the issue.
May be related specifically to this error (ERROR PART1
): 564da523 config_back_db_open: No explicit ACL for back-config configured. Using hardcoded default
(Resource: http://www.openldap.org/doc/admin24/runningslapd.html)
NOTE: I see a few DB related error messages in the verbose log you provided so perhaps it cannot find the applicable DB unless you change to that directory so it can find implicitly unless if supports some other explicit DB pointer method (NOTE2 may be aplicable to this method).
NOTE2: Here's a good read on the LDAP Proxy method and using the uri
, etc. in the configuration this way just to review for something obvious you may be missing or misconfigured in the slapd.conf
file (http://www.openldap.org/faq/data/cache/532.html).
A few Interesting Points from Note2 Section Resource
LDAP Proxy
binddn
bindpw
identity assertion
identity assertion configuration
VERSIONS
Firstly, it appears you are two versions back on OpenLADAP so it may be worth reading the release notes here to see if anything seems applicable to your problem (http://www.openldap.org/software/release/changes.html) which may justify upgrading or running from a test upgrade system if possible.
ERRORS
Secondly, the verbose log detail provides many more error messages, etc. and I wanted to point out ERROR PART 1
, ERROR PART 2
, ERROR PART 3
, and ERROR PART 4
below specificially in that order.
Common causes of LDAP errors
(Resource: http://www.openldap.org/doc/admin24/appendix-common-errors.html)
From what I read up on, if you feel comfortable all your configurations are indeed setup correctly, the ERROR PART 1
first line may indeed just be a "warning" and safe to disgard.
However the line beneath that (~Using hardcoded default
) may be the part per the FIRST section above as I listed the URL, etc.
ERROR PART 1
564da523 config_back_db_open: line 0: warning: cannot assess the validity of the ACL scope within backend naming context
564da523 config_back_db_open: No explicit ACL for back-config configured. Using hardcoded default
Resources:
ERROR PART 2
564da523 <= hdb_dn2id: get failed: DB_NOTFOUND: No matching key/data pair found (-30988)
564da523 <= hdb_dn2id: get failed: DB_NOTFOUND: No matching key/data pair found (-30988)
In this one (above) I found an example here with slapd.conf
files and one (below) stating this so I'm wondering if it's as simple as you needing to change to the DB directory in the slapd.conf
file in your case.
(Resource: http://www.zytrax.com/books/ldap/ch5)
EXAMPLE FROM RESOURCE URL
# root or superuser
rootdn "cn=jimbob, dc=example, dc=com"
rootpw dirtysecret
# The database directory MUST exist prior to running slapd AND
# change path as necessary
directory /var/db/openldap/example-com
ERROR PART 3
Troubleshoot by using telnet <host> <port>
to the LDAP IP address
May be useful as well (http://www.openldap.org/faq/data/cache/532.html)
ldap_read: want=8 error=Resource temporarily unavailable
ERROR PART 4
64da525 <= hdb_dn2id: get failed: DB_NOTFOUND: No matching key/data pair found (-30988)
564da525 => bdb_entry_get: cannot find entry: "cn=melka martin,ou=release engineering,ou=development,ou=research and development,ou=cz,dc=int,dc=company,dc=com"
564da525 QUERY NOT ANSWERABLE
564da525 QUERY CACHEABLE