[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: Replication failed "Operation not allowed on non-leaf"
I wrote a bug report for this
ITS#2512 -> http://www.OpenLDAP.org/its/index.cgi?findid=2512
Hendrik
> -----Original Message-----
> From: Harms, Hendrik (TOJAQ) [SMTP:extern.hendrik.harms@volkswagen.de]
> Sent: Tuesday, April 29, 2003 4:05 PM
> To: 'Fines, Steven'
> Cc: 'openldap-software@OpenLDAP.org'
> Subject: RE: Replication failed "Operation not allowed on non-leaf"
>
> I've checked the replicas. There are not other children left. Only the DN
I
> want to delete left.
>
> For researching the problem I've stopped the slurpd. Then I started the
> delete job. After all selected entries are deleted on the Master I made
> a copy of the replica.log file. Then I started the slurpd again. After
the
> slurpd.status was up to date I found again the "ERROR: Operation not
> allowed on non-leaf" in the rejected log.
> Then I've searched for those entries in my copy of the replica.log file.
> There I found the delete statements not in the right order !
>
> So the slapd already made the mistake. :-(
>
> What to do now?
>
> Hendrik
>
> > -----Original Message-----
> > From: Fines, Steven [SMTP:Steven.Fines@cotelligent.com]
> > Sent: Monday, April 28, 2003 8:42 PM
> > To: Fines, Steven; 'Harms, Hendrik (TOJAQ)'
> > Cc: 'openldap-software@OpenLDAP.org'
> > Subject: RE: Replication failed "Operation not allowed on non-leaf"
> >
> > Oh, I would be lax if I failed to ask this: Have you checked the
replicas
> > that have failed to see if there are other, undeleted, children for
those
> > nodes which are failing?
> >
> > SF
> >
> > -----Original Message-----
> > From: Fines, Steven
> > Sent: Monday, April 28, 2003 11:39 AM
> > To: 'Harms, Hendrik (TOJAQ)'; Fines, Steven
> > Cc: openldap-software@OpenLDAP.org
> > Subject: RE: Replication failed "Operation not allowed on non-leaf"
> >
> > Have you taken a look at the replog file to see if, for some reason, the
> > parent entry is listed to delete before the children? I'm not sure
that's
> > really possible, but if it is than perhaps this is a bug that needs to
be
> > reported...
> >
> > In the interim, you could script something that would programmatically
> > delete the child entries and then the parents (a leaf-to-root deletion).
> >
> > Depending on your programming skills, it wouldn't be too difficult.
> >
> > SF
> >