directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
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 GMT
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>



Mime
View raw message