[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: another CSN too old N-WAY master

To: openldap-technical@openldap.org, Lanfeust troy <lanfeust99@gmail.com>
Subject: Re: another CSN too old N-WAY master
From: "Michael StrÃder" <michael@stroeder.com>
Date: Fri, 04 Oct 2013 12:31:14 +0200
In-reply-to: <CAJ=nZHO+SCS32WYEM6uRGmD8JPcZyD-FVjqABJn33-eaac5Nug@mail.gmail.com>
References: <CAJ=nZHMWFQE_Je4TOPripapM1CH=WCGSEXmt7tsiQeaNKK3o8w@mail.gmail.com> <524170CF.4080104@puzzled.xs4all.nl> <CAJ=nZHN73ztcQ9hRP2Cn4Qn0XphRU=MCmU+7E+Urszw1ykuRgA@mail.gmail.com> <alpine.SOC.2.02.1309241110100.8160@toolbox.rutgers.edu>, <CAJ=nZHO+SCS32WYEM6uRGmD8JPcZyD-FVjqABJn33-eaac5Nug@mail.gmail.com>

On Fri, 4 Oct 2013 11:05:57 +0200 Lanfeust troy <lanfeust99@gmail.com> wrote
> 
> I have upgraded to 2.4.36 openLDAP version. The problem still exists.
> It seem to be appear less than before. This week this problem occur only
> once.

I did not follow your issue in detail.
Are you using slapo-memberof in your deployment?

Ciao, Michael.

Follow-Ups:
- Re: another CSN too old N-WAY master
  - From: Lanfeust troy <lanfeust99@gmail.com>

References:
- Re: another CSN too old N-WAY master
  - From: Lanfeust troy <lanfeust99@gmail.com>

Prev by Date: Re: Q: restrict access using "peername"
Next by Date: Re: another CSN too old N-WAY master
Index(es):
- Chronological
- Thread