Re: Syncrepl replication be_modify failed (18)

["Chris G. Sellers" <cgseller@gmail.com>]

Are you sure that your rules on your slaves are the same - and that  
there is not a contraint that is stopping your deletes from happing on  
the replication?

E.G. can you manually delete the entry w/o warning or error on the  
slaves?   Do you have constraint enforcement enabled ?

Sellers

On Apr 14, 2009, at 11:04 AM, Will Nowak wrote:

> > > add: nisNetgroupTriple
> > > nisNetgroupTriple: (,bobby,shadow)
> > >
> > > At this point, the most recent change gets applied to the master ok,
> > > but it does not get replicated to the slaves. They have a be_modify
> > > failed in their logs:
> > > Apr 13 23:05:43 sl1 slapd[30277]: syncrepl_entry: rid=049  
> > > be_search (0)
> > > Apr 13 23:05:43 sl1 slapd[30277]: syncrepl_entry: rid=049
> > > cn=friends,ou=netgroup,dc=example,dc=com
> > > Apr 13 23:05:43 sl1 slapd[30277]: null_callback : error code 0x12
> > > Apr 13 23:05:43 sl1 slapd[30277]: syncrepl_entry: rid=049  
> > > be_modify (18)
> > > Apr 13 23:05:43 sl1 slapd[30277]: syncrepl_entry: rid=049  
> > > be_modify failed