Re: top-level data entries not replicating, 2.4.15, now 2.4.17

[Brian Neu <proclivity76@yahoo.com>]

I really only created the test2 record to find out why the

   sambaDomainName=SRG,dc=srg,dc=com 

record wasn't replicating.  

This entry won't replicate either, even with a cn attribute . . . 
   dn:cn=test3,dc=srg,dc=com
   objectclass: top
   objectclass: person
   userpassword:blah
   sn:test3
   cn:test3



--- On Fri, 8/21/09, Brett @Google <brett.maxfield@gmail.com> wrote:

> From: Brett @Google <brett.maxfield@gmail.com>
> Subject: Re: top-level data entries not replicating, 2.4.15, now 2.4.17
> To: openldap-technical@openldap.org
> Date: Friday, August 21, 2009, 10:28 AM
> On Sat, Aug 22,
> 2009 at 12:18 AM, Brian Neu <proclivity76@yahoo.com>
> wrote:
> 
> I compiled new rpms and upgraded to 2.4.17 on both the
> provider and consumer.  The problem persists.
> 
> 
> 
> 
> 
> New entries like:
> 
>    dn:cn=test2,dc=srg,dc=com
> 
>    objectclass: top
> 
>    objectclass: person
> 
>    userpassword:blah
> 
>    sn:test2
> 
> 
> If this is literally correct, there is no cn attribute
> (although it is referred to in the dn) ?
>  This would not b considered valid with respect to
> the schema, and as such ignored during replication. I would
> think to get it to slapadd in the first place, schema
> validation would need to have been turned off.
> 
> 
> The other entry you quoted, has a cn value.
> 
> Cheers
> Brett
> 
> 
>