Hi, 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 EOF Thanks, Simon ----- Original Message ----- > From: "Alberto Viana" <albertocrj@xxxxxxxxx> > To: "General discussion list for the 389 Directory server project." <389-users@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Tuesday, March 20, 2018 6:15:46 PM > Subject: [389-users] error moving an user > > Hey Guys, > > 389 version: 389-Directory/1.3.7.4.20170912git26a9426 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 > SLAPI_RESULT_CODE > > 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 -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
