Re: Occasional corrupt DN in be_add logs under 2.4.16

Sean Burford wrote:

slapcat shows no problems with the entry on the 2.4.16 host.

Since the database looks fine I wonder if this is just a logging issue. Should this Debug statement in syncrepl.c actually use op->ora_e->e_name.bv_val or some other attribute?

Looks like a side-effect of ITS#5326. And no, you can't use op->ora_e because the backend may free it before returning (back-bdb/hdb definitely do).

rc = op->o_bd->be_add( op, &rs ); Debug( LDAP_DEBUG_SYNC, "syncrepl_message_to_op: %s be_add %s (%d)\n", si->si_ridtxt, op->o_req_dn.bv_val, rc );

With the exception of si->si_rid becoming si->si_ridtxt (and %d->%s) this Debug statement has not changed since 2.3.