You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@slider.apache.org by bu...@apache.org on 2015/12/16 16:29:26 UTC
svn commit: r975695 - in /websites/staging/slider/trunk/content: ./
docs/manpage.html
Author: buildbot
Date: Wed Dec 16 15:29:26 2015
New Revision: 975695
Log:
Staging update by buildbot for slider
Modified:
websites/staging/slider/trunk/content/ (props changed)
websites/staging/slider/trunk/content/docs/manpage.html
Propchange: websites/staging/slider/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec 16 15:29:26 2015
@@ -1 +1 @@
-1715237
+1720369
Modified: websites/staging/slider/trunk/content/docs/manpage.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/manpage.html (original)
+++ websites/staging/slider/trunk/content/docs/manpage.html Wed Dec 16 15:29:26 2015
@@ -506,13 +506,36 @@ cluster</p>
</pre></div>
+<h3 id="kdiag-keytab-keytab-principal-principal-out-outfile-fail"><code>kdiag [--keytab <keytab> --principal <principal>] [--out outfile] [--fail]</code><a class="headerlink" href="#kdiag-keytab-keytab-principal-principal-out-outfile-fail" title="Permanent link">¶</a></h3>
+<p>Kerberos diagnostics.</p>
+<p>Any information which can be obtained to diagnose Kerberos problems:
+dumping settings, attempting login from a given keytab, etc, etc.</p>
+<p>The purpose here is to have something which can be used to begin to understand
+why the client is having problems talking to Kerberos; a file which can be
+attached to support calls.</p>
+<p>For an example of the output, see [SLIDER-1027|https://issues.apache.org/jira/browse/SLIDER-1027]</p>
+<p>Although there is a <code>--out outfile</code> option, much of the output can come from the JRE
+(to <code>stderr</code>) and via log4j (to <code>stdout</code>). To get all the output, it is best
+to redirect both these output streams to the same file, and omit the <code>--out</code> option.</p>
+<p><code>slider kdiag --keytab zk.service.keytab --principal zookeeper/devix.cotham.uk > out.txt 2>&1</code></p>
+<p>For extra logging during the operation</p>
+<ol>
+<li>Set the environment variable <code>HADOOP_JAAS_DEBUG</code> to <code>true</code>.</li>
+<li>Edit the <code>log4j.properties</code> file for the slider client:<div class="codehilite"><pre><span class="n">log4j</span><span class="p">.</span><span class="n">logger</span><span class="p">.</span><span class="n">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">hadoop</span><span class="p">.</span><span class="n">security</span><span class="p">=</span><span class="n">DEBUG</span>
+</pre></div>
+
+
+</li>
+</ol>
+<p>The diagnostics information currently generated are incomplete. Any contributions
+to this codebase is very welcome.</p>
<h3 id="list-name-live-status-status"><code>list [name] [--live] [--status status]</code><a class="headerlink" href="#list-name-live-status-status" title="Permanent link">¶</a></h3>
<p>List Slider application instances visible to the user. This includes instances
which are on the filesystem.</p>
<p>If no instance name is specified, all instances matching the criteria are listed.</p>
<ol>
<li><code>--live</code> indicates live instances are to be listed: that is anything <code>RUNNING</code>
-or awaiting execution (e.g <code>ACCEPTED</code>) or earlier</li>
+or awaiting execution (e.g <code>ACCEPTED</code>) or earlier.</li>
<li><code>--state <state></code> defines an explicit state for which a record of the cluster
must be found in the RM.</li>
</ol>