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

Re: ContextCSN showing Junk Characters

To: scn_73@yahoo.com
Subject: Re: ContextCSN showing Junk Characters
From: Aaron Richton <richton@nbcs.rutgers.edu>
Date: Thu, 7 Jul 2016 13:38:11 -0400 (EDT)
Cc: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
In-reply-to: <1421912785.254436.1467888527643.JavaMail.yahoo@mail.yahoo.com>
References: <1421912785.254436.1467888527643.JavaMail.yahoo.ref@mail.yahoo.com> <1421912785.254436.1467888527643.JavaMail.yahoo@mail.yahoo.com>
User-agent: Alpine 2.02 (SOC 1266 2009-07-14)

On Thu, 7 Jul 2016, scn_73@yahoo.com wrote:

Hi,

My ldapmaster ContextCSN showing Junk Characters. Please advice how can reset to valid one.

contextCSN:: 0CKRuTQrAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=

CentOS 5.8
Openldap Version is OpenLDAP: slapd 2.3.43

Perhaps some unfortunate corruption bug, but seeing as OpenLDAP 2.3.43 wasreleased 2008/07/16 there's a good chance you can get the appropriate bugfix just by upgrading. Somebody else has probably already contributed thehard work in the past eight years.

So upgrade to the latest version of OpenLDAP from www.openldap.org, andthen any write to the database should write a fresh contextCSN...

Follow-Ups:
- Re: ContextCSN showing Junk Characters
  - From: Clément OUDOT <clement.oudot@savoirfairelinux.com>
- Re: ContextCSN showing Junk Characters
  - From: <scn_73@yahoo.com>

References:
- ContextCSN showing Junk Characters
  - From: <scn_73@yahoo.com>

Prev by Date: Re: How does a client changes from provider to consumer when provider is down
Next by Date: Do you have any recommendations of utilities for manipulating rfc2307 attributes?
Index(es):
- Chronological
- Thread