On 02/23/2016 02:28 PM, Joel Levin wrote:
Odd conundrum - deletion has not been successful on a node with children, or the children itself.

Previously could delete as expected.

Any guidance would be appreciated.

Version: 389-Directory/1.2.11.29 B2014.094.1833 (multi-master: 2 providers, 3 consumers)
I'm afraid this is not the supported version.

For el6 (as well as el6_#), 1.2.11.15-## is the supported version format.

For instance, please see this site: https://www.rpmfind.net/linux/rpm2html/search.php?query=389-ds-base

389-ds-base-1.2.11.15-69.el6_7.i686.html 389 Directory Server (base) Updates for CentOS 6.7 for i386 389-ds-base-1.2.11.15-69.el6_7.i686.rpm
389-ds-base-1.2.11.15-69.el6_7.x86_64.html 389 Directory Server (base) Updates for CentOS 6.7 for x86_64 389-ds-base-1.2.11.15-69.el6_7.x86_64.rpm

We fixed lots of bugs since Apr 4 2014, on that day 389-ds-base-1.2.11.29 was tagged.  Could you please upgrade your system and retry?

Error Log:

[23/Feb/2016:14:13:49 -0800] entryrdn-index - _entryrdn_delete_key: Failed to remove ou=vurs; has children
[23/Feb/2016:14:13:49 -0800] - database index operation failed BAD 1031, err=-1 Unknown error: -1
[23/Feb/2016:14:13:50 -0800] slapi_ldap_bind - Error: could not send bind request for id [cn=replication manager,cn=config] mech [SIMPLE]: error -1 (Can't contact LDAP server) 0 (unknown) 107 (Transport endpoint is not connected)


--
389 users mailing list
389-users@%(host_name)s
http://lists.fedoraproject.org/admin/lists/389-users@lists.fedoraproject.org