Return-Path: <commits-return-47576-archive-asf-public=cust-asf.ponee.io@directory.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 5BA34200BFC
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Sat, 14 Jan 2017 09:07:49 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 5A35D160B35; Sat, 14 Jan 2017 08:07:49 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id A527D160B28
	for <archive-asf-public@cust-asf.ponee.io>; Sat, 14 Jan 2017 09:07:48 +0100 (CET)
Received: (qmail 31143 invoked by uid 500); 14 Jan 2017 08:07:47 -0000
Mailing-List: contact commits-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@directory.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@directory.apache.org>
List-Post: <mailto:commits@directory.apache.org>
List-Id: <commits.directory.apache.org>
Reply-To: dev@directory.apache.org
Delivered-To: mailing list commits@directory.apache.org
Received: (qmail 31133 invoked by uid 99); 14 Jan 2017 08:07:47 -0000
Received: from Unknown (HELO svn01-us-west.apache.org) (209.188.14.144)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Jan 2017 08:07:47 +0000
Received: from svn01-us-west.apache.org (localhost [127.0.0.1])
	by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id 5CE8E3A20D5
	for <commits@directory.apache.org>; Sat, 14 Jan 2017 08:07:47 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1004870 - in /websites/staging/directory/trunk/content: ./
 apacheds/advanced-ug/2.2.1-debian-instance-layout.html
Date: Sat, 14 Jan 2017 08:07:47 -0000
To: commits@directory.apache.org
From: buildbot@apache.org
X-Mailer: svnmailer-1.0.9
Message-Id: <20170114080747.5CE8E3A20D5@svn01-us-west.apache.org>
archived-at: Sat, 14 Jan 2017 08:07:49 -0000

Author: buildbot
Date: Sat Jan 14 08:07:46 2017
New Revision: 1004870

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2.1-debian-instance-layout.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Jan 14 08:07:46 2017
@@ -1 +1 @@
-1778727
+1778728

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2.1-debian-instance-layout.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2.1-debian-instance-layout.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2.1-debian-instance-layout.html Sat Jan 14 08:07:46 2017
@@ -312,6 +312,15 @@ h2:hover > .headerlink, h3:hover > .head
 
 
 <p>Again, you must provide the instance name if it's not the default one</p>
+<h2 id="repairing-the-indexes">Repairing the indexes<a class="headerlink" href="#repairing-the-indexes" title="Permanent link">&para;</a></h2>
+<p>Sometime, the database get corrupted. Hopefully, this is not frequent, but when it happens, it left you in a position where there is nothing you can do but re-injecting a backup.</p>
+<p>That is more than annoying, and the latest version (2.0.0-M23) as an added feature that allows you to repair the indexes (this is a best effort, it might not work in all cases). Here is the step to follow in order to run the tool :</p>
+<div class="codehilite"><pre>$ <span class="n">sudo</span> <span class="o">/</span><span class="n">etc</span><span class="o">/</span><span class="n">init</span><span class="p">.</span><span class="n">d</span><span class="o">/</span><span class="n">apacheds</span><span class="o">-&lt;</span><span class="n">version</span><span class="o">&gt;</span> <span class="n">repair</span> <span class="o">/</span><span class="n">var</span><span class="o">/</span><span class="n">lib</span><span class="o">/</span><span class="n">apacheds</span><span class="o">-&lt;</span><span class="n">version</span><span class="o">&gt;/&lt;</span><span class="n">instance</span><span class="o">&gt;</span>
+</pre></div>
+
+
+<p>All the indexes will be recreated, based on the content of the master table (which contains all the entries). You can also remove all the database files but the master.db and master.lg files from each user partitions in /var/lib/apacheds-<version>/<instance>/partitions, before running the command.</p>
+<p>The server should restart with a working database (it might take a bit of time, but not that much : rebuilding indexes is orders of magnitude faster than injcting entries in the server).</p>
 <h2 id="logs">Logs<a class="headerlink" href="#logs" title="Permanent link">&para;</a></h2>
 <p>You can check what's going on in the <em>apacheds-&lt;version&gt;instances/&lt;instance-name&gt;/log/apacheds.log</em> file, which is created using the configuration set in <em>apacheds-&lt;version&gt;instances/&lt;instance-name&gt;/conf/log4j.properties</em>.</p>
 <p>Typically, when you start the server, you will get such log :</p>