rahul.manchanda@bt.com writes:
Hi ,
I have added sync_use_subentry in the ldap configuration and it started throwing the core dump while performing the sync from other running server and stops the LDAP process.
Did you run the core within gdb?
Here is the error seen the in the debug logs.
<= index_entry_add( 114, "ou=New NetIQ StAlbans / Glasgow,ou=ChartReports,ou= services,o=BT" ) success
=> entry_encode(0x00000072): ou=New NetIQ StAlbans / Glasgow,ou= ChartReports,ou=services,o=BT
<= entry_encode(0x00000072): ou=New NetIQ StAlbans / Glasgow,ou= ChartReports,ou=services,o=BT
bdb_add: added id=00000072 dn="ou=New NetIQ StAlbans / Glasgow,ou= ChartReports,ou=services,o=BT"
send_ldap_result: conn=-1 op=0 p=0
send_ldap_result: err=0 matched="" text=""
bdb_modify: cn=ldapsync,o=bt
bdb_dn2entry("cn=ldapsync,o=bt")
=> bdb_dn2id("cn=ldapsync,o=bt")
<= bdb_dn2id: get failed: DB_NOTFOUND: No matching key/data pair found (-30988)
bdb_modify: dn2entry failed (-30988)
who is running slapd and who is the owner of dn2id.bdb and dn2entry.bdb?
send_ldap_result: conn=-1 op=0 p=0
send_ldap_result: err=10 matched="o=BT" text=""
error 10 indicates that the referral is not available.
./start_ldap.sh: line 3: 14900 Segmentation Fault (core dumped) /software /openldap2.4.22/libexec/slapd -f /software/openldap2.4.22/etc/openldap/ slapd.conf -h ldap://tardis02.nat.bt.com:489/ -d -1
Have attached the slapd.conf file.
Could you please suggest?
Your slapd.conf is completely bogus, don't mix global configuration parameters with database specific parameters, and vice versa. Overlay declarations have to follow all database configuration parameters.
overlay syncprov syncprov-checkpoint 100 5 syncprov-sessionlog 100
sync_use_subentry TRUE
^^^^^^^^^^^^^^^^^^^^^^^^
this is a database specific parameter
# Index Definition
[...]
Indices are database specific
############################# ###### ACL definitions ###### #############################
ACL's are partly global and database specific
-Dieter