[Date Prev][Date Next]
Re: (ITS#4695) syncrepl modrdn failing with garbage returned by bdb_dn2entry
Quanah Gibson-Mount wrote:
> --On Wednesday, October 04, 2006 6:06 PM +0000 firstname.lastname@example.org wrote:
>> Full_Name: Tim Kay
>> OS: Linux (Fedora core 5 RPM)
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (184.108.40.206)
>> Modifying a DN on the syncrepl provider fails to propogate to the
>> consumer. The provider "sends" a valid modify but the consumer, having
>> received the modify request walks the tree, returns the parent DN to the
>> entry, determines that write access is permitted and the iterates, at
>> this point newSuperior->bv_val is set to "*" !? bdb_dn2entry is now
>> searching for "�UUU" which looks like some unicode screw up.
> You didn't provide an OpenLDAP version. I'll note that if you intend to
> use syncrepl, use OpenLDAP 2.3.27 (or later).
Sorry Quanah (and everyone else),
The identical problem is happening in both 2.3.27 and 2.3.19 with both
the bdb and ldbm back ends.
> Quanah Gibson-Mount
> Principal Software Developer
> ITS/Shared Application Services
> Stanford University
> GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html