Chun Tat David Chu wrote:
Hi,
I am not sure if this should belong to the openldap mailing list or here,
but I will try here first since I'm using Fedora DS.
I have "openldap-clients.i386 version 2.3.27-8" binary package installed,
and using it to talk to Fedora-DS 1.0.2.
I use ldapmodify to import data into the ldap server.
The command I use is
ldapmodify -h <hostname> -p <port> -D "cn=Directory Manager" -w
<pw> -f
./data.ldif -x
And the data looks like this
ou=test1,dc=sandbox,dc=com
ou=test11,ou=test1,dc=sandbox,dc=com
ou=test12,ou=test1,dc=sandbox,dc=com
ou=test13,ou=test1,dc=sandbox,dc=com
I then use ldapdelete to recursively delete all data.
The command I use is
ldapdelete -h <hostname> -p <port> -D "cn=Directory Manager" -w
<pw> -f
./delete.ldif -x -r -v
And the delete.ldif looks like this
ou=test1,dc=sandbox,dc=com
When I ran the ldapdelete command, it prints out this
deleting entry "ou=test1,dc=sandbox,dc=com"
deleting children of: ou=test1,dc=sandbox,dc=com
ldap_search: Critical extension is unavailable (12)
The deletion did succeeded, but I just couldn't figure out why it prints out
"Critical extension is unavailable".
This only happen when I start using openldap-client 2.3.27-8. It didn't
happen when I use openldap-clients-2.2.13-3.
Any idea why it prints out "Critical extension is unavailable"?
OpenLDAP's ldapdelete was modified to be able to remove a subentry
related to replication that was used at some point within syncrepl.
However, that code erroneously assumed that the database being deleted
always supported subentries, which wasn't true even for OpenLDAP itself.
It was fixed as ITS#5293 <
http://www.openldap.org/its?findid=5293> in
2.4.8, but it hasn't been fixed in the 2.3 series.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
---------------------------------------
Office: +39 02 23998309
Mobile: +39 333 4963172
Email: pierangelo.masarati(a)sys-net.it
---------------------------------------