Hi,
I am encountered a problem regarding the checking of the directory structure during ldapsearch request. I did slapadd on my LDAP server (OpenLDAP 2.4.44 with MDB backend) for few entries and found the below error as my top entry "ou=people,dc=my-domain,dc=com" was missing from the DB. ############################################################################### /usr/local/sbin/slapadd -v -c -w -f /usr/local/etc/openldap/slapd.conf -l 2_tmp.ldif
578c3c23 mdb_monitor_db_open: monitoring disabled; configure monitor database to enable added: "ou=Test1,ou=people,dc=my-domain,dc=com" (00000005) added: "ou=Test2,ou=people,dc=my-domain,dc=com" (00000006) added: "ou=Test3,ou=people,dc=my-domain,dc=com" (00000007) added: "ou=Test4,ou=people,dc=my-domain,dc=com" (00000008) _#################### 100.00% eta none elapsed none fast! modified: "(null)" (00000001) Closing DB...Error, entries missing! entry 4: ou=people,dc=my-domain,dc=com ###############################################################################
The above error is fine. Do the above entries get added to the DB, though the parent node for these entries was not present?
Because when I search for the entry using the below ldapsearch command, this gives me the correct result. ############################################################################### ldapsearch -x -D cn=Manager, dc=my-domain,dc=com -w secret -b ou=Test1,ou=people, dc=my-domain,dc=com -s sub "(&(objectclass=organizationalUnit)(ou=Test1*))" -H ldap://0.0.0.0:2016
# extended LDIF # # LDAPv3 # base <ou=Test1,ou=people,dc=my-domain,dc=com> with scope subtree # filter: (&(objectclass=organizationalUnit)(ou=Test1*)) # requesting: ALL #
# Test1, people, my-domain.com dn: ou=Test1,ou=people, dc=my-domain,dc=com ou: Test1 objectClass: organizationalUnit companyName: Test1
# search result search: 2 result: 0 Success
# numResponses: 2 # numEntries: 1 ###############################################################################
Does this means ldapsearch check just for the specific entry and not the complete directory structure? Thanks in advance.
Regards, Gurjot Kaur
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
--On Monday, July 18, 2016 10:02 AM +0000 Gurjot Kaur gurjot.kaur@aricent.com wrote:
Hi,
I am encountered a problem regarding the checking of the directory structure during ldapsearch request. I did slapadd on my LDAP server (OpenLDAP 2.4.44 with MDB backend) for few entries and found the below error as my top entry "ou=people,dc=my-domain,dc=com" was missing from the DB. ############################################################################### /usr/local/sbin/slapadd -v -c -w -f /usr/local/etc/openldap/slapd.conf -l 2_tmp.ldif
578c3c23 mdb_monitor_db_open: monitoring disabled; configure monitor database to enable added: "ou=Test1,ou=people,dc=my-domain,dc=com" (00000005) added: "ou=Test2,ou=people,dc=my-domain,dc=com" (00000006) added: "ou=Test3,ou=people,dc=my-domain,dc=com" (00000007) added: "ou=Test4,ou=people,dc=my-domain,dc=com" (00000008) _#################### 100.00% eta none elapsed none fast! modified: "(null)" (00000001) Closing DB...Error, entries missing! entry 4: ou=people,dc=my-domain,dc=com ###############################################################################
The above error is fine. Do the above entries get added to the DB, though the parent node for these entries was not present?
A glue entry will be created for the missing parent, so that the db import can succeed. However, you really should fix your database instead.
--Quanah
--
Quanah Gibson-Mount
openldap-technical@openldap.org