Friday, March 23, 2018

[389-users] Re: error moving an user


I was able to reproduce the problem in a new fresh install (I just imported my database), and It's related to "Referential Integrity Postoperation Plugin" that I use in my environment. When I disable it, the moving works just fine.

I have a single master, replication to one AD. 

I changed the log level, but it's really hard to find the root cause.

Do you want to take a look on it?

Once it has some info about my tree, I'd prefer to send the link to download the file directly to you.


On Wed, Mar 21, 2018 at 12:00 PM, Simon Pichugin <> wrote:
could you please enable 16385 errorlog-level (16384 defaults and 1 trace) just before the operation and send us the /var/log/dirsrv/slapd-INSTNAME/errors:

ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w password << EOF
dn: cn=config
changetype: modify
replace: nsslapd-errorlog-level
nsslapd-errorlog-level: 16385


----- Original Message -----
> From: "Alberto Viana" <>
> To: "General discussion list for the 389 Directory server project." <>
> Sent: Tuesday, March 20, 2018 6:15:46 PM
> Subject: [389-users] error moving an user
> Hey Guys,
> 389 version: 389-Directory/ B2017.255.1330
> I'm trying to move one of my users to another OU and I see this kind of
> error:
> Error while moving entry
> - [LDAP: error code 1 - Operations Error]
> java.lang.Exception: [LDAP: error code 1 - Operations Error]
> at
> In the log I see:
> [20/Mar/2018:14:12:27.172553808 -0300] - ERR - ldbm_back_modrdn -
> SLAPI_PLUGIN_BE_TXN_POST_MODRDN_FN plugin returned error but did not set
> I thought that was related to my windows replication, but I disabled it and
> I'm still getting the error.
> Any clues?
> _______________________________________________
> 389-users mailing list --
> To unsubscribe send an email to
389-users mailing list --
To unsubscribe send an email to

No comments:

Post a Comment