Hi Morgan,
I'm afraid you are facing the damning database that we know of for years.
We have added a 'repair' features that tries to fix a broken database,
as much as possible. It's not 100% guaranteed though. What it does is it
reads the master database and rebuild all the indexes from it - if the
master database is not broken itself -.
You can try it by starting the server using the 'repair' command instead
of the 'start' command. It will try to repair the indexes and then start
the server. If it does not work, then there is little you can do but
reinjecting a backup :/ You need to be running ApacheDS -2.0.0-M24 to
benefit from this feature.
I'm currently working as fast as I can to get Mavibot worki,ng a s a
replacement for the current database. It's not supposed to be corrupted
in any way. Sadly, I have very little time to dedicate on that work atm...
On 04/11/2019 17:34, Morgan Miskell wrote:
We have an ApacheDS implementation that just dropped from 12500 users
to about 330 or so. We are trying to debug what happened. Are there
any database integrity tools that we could run to determine if there
was corruption or a database issue inside LDAP? Do you have any
vendors that can support ApacheDS professionally and assist us with
debugging the root cause if we are interested in pursuing?
Morgan Miskell
Infrastructure Manager
*Direct ChassisLink, Inc.*
3525 Whitehall Park Drive
Suite 400
Charlotte, NC 28273
Office: (704) 461-0926
[email protected] <mailto:[email protected]>
cid:[email protected]
<https://www.facebook.com/directchassislink/>cid:[email protected]
<https://www.linkedin.com/company/direct-chassislink-inc-/>cid:[email protected]
<https://twitter.com/DCLItweets>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
