Re: replication crashes 1 of 2 servers - after working for months

["Chris G. Sellers" <Chris.Sellers@nitle.org>]

Okay,

Follow-up for the good of the group.  I regressed, and it seemed the  
errors started to trigger when I enabled indexing of the attributes of  
entryCSN and entryUUID.

I've kept those off now, along with the unique overlay for the  
attribute uidNumber because that seemed to be causing me problem too  
but that could be my bad data.  I'm going to let it run this way for a  
while to see if it's stable.

I'll keep the thread up-to-date with details for the good of others.   
A trace may be in the future

Sellers

On Jul 15, 2008, at 5:04 PM, Quanah Gibson-Mount wrote:

> --On Tuesday, July 15, 2008 3:20 PM -0400 "Chris G. Sellers" <Chris.Sellers@nitle.org 
> > wrote:
>
> > Nope, that didn't seem to impact it (as some of you probably were  
> > about
> > to say).
> >
> >
> > I do notice that after it crashes a few times my dc=nitle,dc=org gets
> > clobbered and becomes objectClass=glue instead of  
> > objectClass=dcObject  -
> > which renders the tree useless.
>
> What release are you running?
>
> You may want to try the OPENLDAP_REL_ENG_2_4 tree.  2.4.11 will  
> hopefully be out this week.
>
> --Quanah
>
>
> --
>
> Quanah Gibson-Mount
> Principal Software Engineer
> Zimbra, Inc
> --------------------
> Zimbra ::  the leader in open source messaging and collaboration

++++++++++++++++++++++++++++++++++++++
Chris G. Sellers	|  Internet Engineer      |   NITLE
734.661.2318	|  chris.sellers@nitle.org
Jabber: csellers@nitle.org  | AIM: imthewherd