We would need to test this scenario, but it could very likely be a bug in the server.
To be sure the conditions you have here are:
ou=start,dc=…
ou=destination,dc=…
In ou=start you have 800+ entries.
Then you are doing a modrdn of ou=start to ou=start,ou=destination,dc=…, and the error
condition occurs?
Is this correct?
On 21 Feb 2019, at 02:49, Olivier JUDITH <gnulux(a)gmail.com>
wrote:
Hi,
I have activated Referential Integrity plugin on my instance in order to move several OU
to a new parent subtree. Also to update automatically uniqueMember attribute defined in
group member .
It works fine with few user entries under some OU but fails when the OU contains more
than 400 entries or somtime more than 800.
The error from the 389-console is :
ou=UNITA, OU=Accounts,dc=mydomain,dc=com: netscape.ldap.LDAPException: error result (1);
Operations error.
In error file
[20/Feb/2019:17:37:59.123749991 +0100] - ERR - ldbm_back_modrdn -
SLAPI_PLUGIN_BE_TXN_POST_MODRDN_FN plugin returned error but did not set
SLAPI_RESULT_CODE
After this error the OU : UNITA, OU=Accounts,dc=mydomain,dc=com is not visible from
389-console . I have to restart the instance in order to recover the OU.
Did i miss something in my configuration or do i have to set a specific parameter to
support big entries ?
My installation : 389DS 1.3.6 .
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
—
Sincerely,
William Brown
Software Engineer, 389 Directory Server
SUSE Labs