doc/_images doc/index.html doc/searchindex.js doc/_sources

[Adam Stokes]

 doc/_images/cas_logo.png |binary
 doc/_sources/index.txt   |  152 +++++++++++++++++++++++++++++++++++++++++++++--
 doc/index.html           |  140 +++++++++++++++++++++++++++++++++++++++++--
 doc/searchindex.js       |    2 
 4 files changed, 282 insertions(+), 12 deletions(-)

New commits:
commit d065bc0f844853d7d7dffd5b96a63a2da5e137ee
Author: Adam Stokes <uzr(a)rambos.knife&gt;
Date:   Wed Feb 11 09:34:06 2009 -0500

    - Updated documentation to provide analyzing and troubleshooting
      sections

diff --git a/doc/_images/cas_logo.png b/doc/_images/cas_logo.png
new file mode 100644
index 0000000..39e2302
Binary files /dev/null and b/doc/_images/cas_logo.png differ
diff --git a/doc/_sources/index.txt b/doc/_sources/index.txt
index aac3fcb..418e0ab 100644
--- a/doc/_sources/index.txt
+++ b/doc/_sources/index.txt
@@ -1,5 +1,7 @@
-Core Analysis System (CAS)
-==========================
+.. image:: cas_logo.png
+
+Core Analysis System
+====================
 
 Introduction
 ------------
@@ -92,8 +94,8 @@ version of crash is installed this directive can be set to the crash
binary
 and CAS will automatically process x86 cores on a x86_64 machine. ``Note`` this
 is only available if the CAS server is a x86_64 machine.
 
-Setup
------
+Setup & Execution
+-----------------
 
 Preparing CAS Server
 ^^^^^^^^^^^^^^^^^^^^
@@ -192,10 +194,152 @@ initial analysis to the specified email address. From there further
instructions
 are provided in either the email or the ``process log`` on how to access and analyze
 the core.
 
+Analyzing
+---------
+
+Continuing with the previous example the results of CAS processing should be emailed
+and look something similar to::
+
+    Subject: CAS results for 12345
+    Date: Wed, 11 Feb 2009 08:44:37 -0500
+    
+    Location: /cores/processed/12345/02.11.09.08.44.19
+    Server: test-2.gss.redhat.com
+    Output data:
+    PID: 0      TASK: ffffffff803e9b80  CPU: 0   COMMAND: "swapper"
+     #0 [ffffffff8047a0a0] smp_call_function_interrupt at ffffffff8011d191
+     #1 [ffffffff8047a0b0] call_function_interrupt at ffffffff80110bf5
+    --- <IRQ stack> ---
+     #2 [ffffffff80529f08] call_function_interrupt at ffffffff80110bf5
+        [exception RIP: default_idle+32]
+        RIP: ffffffff8010e7a9  RSP: ffffffff80529fb8  RFLAGS: 00000246
+        RAX: 0000000000000000  RBX: 0000000000000000  RCX: 0000000000000018
+        RDX: ffffffff8010e789  RSI: ffffffff803e9b80  RDI: 0000010008001780
+        RBP: 0000000000000000   R8: ffffffff80528000   R9: 0000000000000080
+        R10: 0000000000000100  R11: 0000000000000004  R12: 0000000000000000
+        R13: 0000000000000000  R14: 0000000000000000  R15: 0000000000000000
+        ORIG_RAX: fffffffffffffffa  CS: 0010  SS: 0018
+     #3 [ffffffff80529fb8] cpu_idle at ffffffff8010e81c
+    
+    PID: 0      TASK: 100f57cb030       CPU: 1   COMMAND: "swapper"
+     #0 [1000107bfa0] smp_call_function_interrupt at ffffffff8011d191
+     #1 [1000107bfb0] call_function_interrupt at ffffffff80110bf5
+    --- <IRQ stack> ---
+     #2 [10001073e98] call_function_interrupt at ffffffff80110bf5
+        [exception RIP: default_idle+32]
+        RIP: ffffffff8010e7a9  RSP: 0000010001073f48  RFLAGS: 00000246
+        RAX: 0000000000000000  RBX: 0000000000000e86  RCX: 0000000000000018
+        RDX: ffffffff8010e789  RSI: 00000100f57cb030  RDI: 00000102000a4780
+        RBP: 0000000000000001   R8: 0000010001072000   R9: 0000000000000040
+        R10: 0000000000000000  R11: 0000000000000008  R12: 0000000000000000
+        R13: 0000000000000000  R14: 0000000000000000  R15: 0000000000000000
+        ORIG_RAX: fffffffffffffffa  CS: 0010  SS: 0018
+     #3 [10001073f48] cpu_idle at ffffffff8010e81c
+    
+    PID: 6122   TASK: 101f3658030       CPU: 2   COMMAND: "gfs_quotad"
+     #0 [101f21efb20] start_disk_dump at ffffffffa03183ff
+     #1 [101f21efb50] try_crashdump at ffffffff8014cc1d
+     #2 [101f21efb60] die at ffffffff80111c90
+     #3 [101f21efb80] do_invalid_op at ffffffff80112058
+     #4 [101f21efc40] error_exit at ffffffff80110e1d
+        [exception RIP: do_dlm_lock+366]
+
+    ... snip ...
+
+From this email a ``location`` is provided ``/cores/processed/12345/02.11.09.08.44.19``
+and the server in which further analyzation can be continued ``test-2.gss.redhat.com``.
+
+Normally from a support perspective this email should contain enough information
+for a kernel engineer to begin debugging the problem. Assuming more is needed
+the information provided previously will prove beneficial for anyone wishing
+to access this data.
+
+Logging into the stated server and changing into the directory defined several
+files are presented::
+
+    $ pwd
+    /cores/processed/12345/02.11.09.08.44.19 
+    $ ls
+    12345.log  crash  crash.in  crash.out  usr  vmcore.12345
+
+``12345.log``: contains any informational messages presented during the processing
+of the core. Everything from informational to debug statements are provided here.
+
+``crash``: a script autogenerated to provide an automated way of gathering intial
+data from the coredump. ``Note`` if wanting to use this crash wrapper in a more
+manual approach some alterations to the script need to occur.
+
+crash wrapper in its original form::
+
+    #!/bin/sh
+    /usr/bin/crash /cores/processed/12345/02.11.09.08.44.19/vmcore.12345
/cores/processed/12345/02.11.09.08.44.19/usr/lib/debug/lib/modules/2.6.9-78.18.ELlargesmp/vmlinux
-s < /cores/processed/12345/02.11.09.08.44.19/crash.in
+
+In order to remove automation the redirect from crash.in needs to be removed::
+
+    #!/bin/sh
+    /usr/bin/crash /cores/processed/12345/02.11.09.08.44.19/vmcore.12345
/cores/processed/12345/02.11.09.08.44.19/usr/lib/debug/lib/modules/2.6.9-78.18.ELlargesmp/vmlinux
+
+**Alternative to using the crash wrapper**
+
+It is possible to specify the vmlinux and corefile with crash on the command line::
+
+    $ crash
/cores/processed/12345/02.11.09.08.44.19/usr/lib/debug/lib/modules/2.6.9-78.18.ELlargesmp/vmlinux
/cores/processed/12345/02.11.09.08.44.19/vmcore.12345
+
+``crash.in``: a list of commands to be read into crash during the automated
+analysis::
+
+    bt -a >>/cores/processed/12345/02.11.09.08.44.19/crash.out
+    sys >>/cores/processed/12345/02.11.09.08.44.19/crash.out
+    log >>/cores/processed/12345/02.11.09.08.44.19/crash.out
+    mod >>/cores/processed/12345/02.11.09.08.44.19/crash.out
+    exit
+
+``crash.out``: output of initial crash analysis and the same data which
+is sent in an email if defined.
+
+``usr``: directory structure from the extraction of the vmlinux file
+from the associated kernel-debuginfo rpm for use within crash::
+
+   
/cores/processed/12345/02.11.09.08.44.19/usr/lib/debug/lib/modules/2.6.9-78.18.ELlargesmp/vmlinux
+
+``vmcore.12345``: corefile from which was either defined or extracted from
+a compressed archive during CAS initialization.
+
+Troubleshooting
+---------------
+
+Some of the major problems that arise when using CAS usually boils down to some
+improper usage of the compression and archiving tools.
+
+When compressing a core which may need to be sent over the network to a CAS server
+one of the proper ways to do so is::
+
+    $ tar cvjf vmcore.12345.tar.bz2 vmcore.12345
+
+Other various ways of compressing archive are as follows::
+
+    $ tar cvzf vmcore.tar.gz vmcore 
+    $ gzip vmcore 
+    $ bzip2 vmcore 
+
+``Note``: please do not double compress or CAS will fail.
+
+Another issue, which isn't primarily a fault of CAS, are
+incomplete or corrupted cores. If either of these occur
+there is a chance that CAS will not be able to process
+the data needed to associate a debug kernel or do any
+sort of automated analysis. Unfortunately, there is not
+much that can be done to resolve these sort of issues
+other than verifying that the process which happens when
+a system coredump and when that dump reaches the
+system specified for retrieval is solid and are seeing
+no errors.
+
 Resources
 =========
 
 * `CAS Wiki <http://fedorahosted.org/cas>`_
+* `CAS FAQ <https://fedorahosted.org/cas/wiki/CasFAQ>`_
 * `Mailing list <https://fedorahosted.org/mailman/listinfo/cas>`_
 * `Upstream releases <https://fedorahosted.org/releases/c/a/cas/>`_
 * Checkout latest from Git, ``git clone git://git.fedorahosted.org/cas.git``
diff --git a/doc/index.html b/doc/index.html
index 5ee6297..72522e1 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta http-equiv="Content-Type" content="text/html;
charset=utf-8" />
     
-    <title>Core Analysis System (CAS) &mdash; CAS v0.13-118
documentation</title>
+    <title>Core Analysis System &mdash; CAS v0.13-118
documentation</title>
     <link rel="stylesheet" href="_static/default.css"
type="text/css" />
     <link rel="stylesheet" href="_static/pygments.css"
type="text/css" />
     <script type="text/javascript">
@@ -37,8 +37,9 @@
           <div class="body">
             
   
-  <div class="section" id="core-analysis-system-cas">
-<h1>Core Analysis System (CAS)<a class="headerlink"
href="#core-analysis-system-cas" title="Permalink to this
headline">¶</a></h1>
+  <img alt="_images/cas_logo.png" src="_images/cas_logo.png"
/>
+<div class="section" id="core-analysis-system">
+<h1>Core Analysis System<a class="headerlink"
href="#core-analysis-system" title="Permalink to this
headline">¶</a></h1>
 <div class="section" id="introduction">
 <h2>Introduction<a class="headerlink" href="#introduction"
title="Permalink to this headline">¶</a></h2>
 <div class="section" id="description">
@@ -113,8 +114,8 @@ and CAS will automatically process x86 cores on a x86_64 machine.
<tt class="doc
 is only available if the CAS server is a x86_64 machine.</p>
 </div>
 </div>
-<div class="section" id="setup">
-<h2>Setup<a class="headerlink" href="#setup"
title="Permalink to this headline">¶</a></h2>
+<div class="section" id="setup-execution">
+<h2>Setup &amp; Execution<a class="headerlink"
href="#setup-execution" title="Permalink to this
headline">¶</a></h2>
 <div class="section" id="preparing-cas-server">
 <h3>Preparing CAS Server<a class="headerlink"
href="#preparing-cas-server" title="Permalink to this
headline">¶</a></h3>
 <p>To install the CAS package simply type:</p>
@@ -199,11 +200,134 @@ are provided in either the email or the <tt class="docutils
literal"><span class
 the core.</p>
 </div>
 </div>
+<div class="section" id="analyzing">
+<h2>Analyzing<a class="headerlink" href="#analyzing"
title="Permalink to this headline">¶</a></h2>
+<p>Continuing with the previous example the results of CAS processing should be
emailed
+and look something similar to:</p>
+<div class="highlight-python"><pre>Subject: CAS results for 12345
+Date: Wed, 11 Feb 2009 08:44:37 -0500
+
+Location: /cores/processed/12345/02.11.09.08.44.19
+Server: test-2.gss.redhat.com
+Output data:
+PID: 0      TASK: ffffffff803e9b80  CPU: 0   COMMAND: "swapper"
+ #0 [ffffffff8047a0a0] smp_call_function_interrupt at ffffffff8011d191
+ #1 [ffffffff8047a0b0] call_function_interrupt at ffffffff80110bf5
+--- &lt;IRQ stack&gt; ---
+ #2 [ffffffff80529f08] call_function_interrupt at ffffffff80110bf5
+    [exception RIP: default_idle+32]
+    RIP: ffffffff8010e7a9  RSP: ffffffff80529fb8  RFLAGS: 00000246
+    RAX: 0000000000000000  RBX: 0000000000000000  RCX: 0000000000000018
+    RDX: ffffffff8010e789  RSI: ffffffff803e9b80  RDI: 0000010008001780
+    RBP: 0000000000000000   R8: ffffffff80528000   R9: 0000000000000080
+    R10: 0000000000000100  R11: 0000000000000004  R12: 0000000000000000
+    R13: 0000000000000000  R14: 0000000000000000  R15: 0000000000000000
+    ORIG_RAX: fffffffffffffffa  CS: 0010  SS: 0018
+ #3 [ffffffff80529fb8] cpu_idle at ffffffff8010e81c
+
+PID: 0      TASK: 100f57cb030       CPU: 1   COMMAND: "swapper"
+ #0 [1000107bfa0] smp_call_function_interrupt at ffffffff8011d191
+ #1 [1000107bfb0] call_function_interrupt at ffffffff80110bf5
+--- &lt;IRQ stack&gt; ---
+ #2 [10001073e98] call_function_interrupt at ffffffff80110bf5
+    [exception RIP: default_idle+32]
+    RIP: ffffffff8010e7a9  RSP: 0000010001073f48  RFLAGS: 00000246
+    RAX: 0000000000000000  RBX: 0000000000000e86  RCX: 0000000000000018
+    RDX: ffffffff8010e789  RSI: 00000100f57cb030  RDI: 00000102000a4780
+    RBP: 0000000000000001   R8: 0000010001072000   R9: 0000000000000040
+    R10: 0000000000000000  R11: 0000000000000008  R12: 0000000000000000
+    R13: 0000000000000000  R14: 0000000000000000  R15: 0000000000000000
+    ORIG_RAX: fffffffffffffffa  CS: 0010  SS: 0018
+ #3 [10001073f48] cpu_idle at ffffffff8010e81c
+
+PID: 6122   TASK: 101f3658030       CPU: 2   COMMAND: "gfs_quotad"
+ #0 [101f21efb20] start_disk_dump at ffffffffa03183ff
+ #1 [101f21efb50] try_crashdump at ffffffff8014cc1d
+ #2 [101f21efb60] die at ffffffff80111c90
+ #3 [101f21efb80] do_invalid_op at ffffffff80112058
+ #4 [101f21efc40] error_exit at ffffffff80110e1d
+    [exception RIP: do_dlm_lock+366]
+
+... snip ...</pre>
+</div>
+<p>From this email a <tt class="docutils literal"><span
class="pre">location</span></tt> is provided <tt
class="docutils literal"><span
class="pre">/cores/processed/12345/02.11.09.08.44.19</span></tt>
+and the server in which further analyzation can be continued <tt class="docutils
literal"><span
class="pre">test-2.gss.redhat.com</span></tt>.</p>
+<p>Normally from a support perspective this email should contain enough
information
+for a kernel engineer to begin debugging the problem. Assuming more is needed
+the information provided previously will prove beneficial for anyone wishing
+to access this data.</p>
+<p>Logging into the stated server and changing into the directory defined several
+files are presented:</p>
+<div class="highlight-python"><pre>$ pwd
+/cores/processed/12345/02.11.09.08.44.19
+$ ls
+12345.log  crash  crash.in  crash.out  usr  vmcore.12345</pre>
+</div>
+<p><tt class="docutils literal"><span
class="pre">12345.log</span></tt>: contains any informational
messages presented during the processing
+of the core. Everything from informational to debug statements are provided
here.</p>
+<p><tt class="docutils literal"><span
class="pre">crash</span></tt>: a script autogenerated to provide
an automated way of gathering intial
+data from the coredump. <tt class="docutils literal"><span
class="pre">Note</span></tt> if wanting to use this crash wrapper
in a more
+manual approach some alterations to the script need to occur.</p>
+<p>crash wrapper in its original form:</p>
+<div class="highlight-python"><pre>#!/bin/sh
+/usr/bin/crash /cores/processed/12345/02.11.09.08.44.19/vmcore.12345
/cores/processed/12345/02.11.09.08.44.19/usr/lib/debug/lib/modules/2.6.9-78.18.ELlargesmp/vmlinux
-s &lt; /cores/processed/12345/02.11.09.08.44.19/crash.in</pre>
+</div>
+<p>In order to remove automation the redirect from crash.in needs to be
removed:</p>
+<div class="highlight-python"><pre>#!/bin/sh
+/usr/bin/crash /cores/processed/12345/02.11.09.08.44.19/vmcore.12345
/cores/processed/12345/02.11.09.08.44.19/usr/lib/debug/lib/modules/2.6.9-78.18.ELlargesmp/vmlinux</pre>
+</div>
+<p><strong>Alternative to using the crash wrapper</strong></p>
+<p>It is possible to specify the vmlinux and corefile with crash on the command
line:</p>
+<div class="highlight-python"><pre>$ crash
/cores/processed/12345/02.11.09.08.44.19/usr/lib/debug/lib/modules/2.6.9-78.18.ELlargesmp/vmlinux
/cores/processed/12345/02.11.09.08.44.19/vmcore.12345</pre>
+</div>
+<p><tt class="docutils literal"><span
class="pre">crash.in</span></tt>: a list of commands to be read
into crash during the automated
+analysis:</p>
+<div class="highlight-python"><pre>bt -a
&gt;&gt;/cores/processed/12345/02.11.09.08.44.19/crash.out
+sys &gt;&gt;/cores/processed/12345/02.11.09.08.44.19/crash.out
+log &gt;&gt;/cores/processed/12345/02.11.09.08.44.19/crash.out
+mod &gt;&gt;/cores/processed/12345/02.11.09.08.44.19/crash.out
+exit</pre>
+</div>
+<p><tt class="docutils literal"><span
class="pre">crash.out</span></tt>: output of initial crash
analysis and the same data which
+is sent in an email if defined.</p>
+<p><tt class="docutils literal"><span
class="pre">usr</span></tt>: directory structure from the
extraction of the vmlinux file
+from the associated kernel-debuginfo rpm for use within crash:</p>
+<div
class="highlight-python"><pre>/cores/processed/12345/02.11.09.08.44.19/usr/lib/debug/lib/modules/2.6.9-78.18.ELlargesmp/vmlinux</pre>
+</div>
+<p><tt class="docutils literal"><span
class="pre">vmcore.12345</span></tt>: corefile from which was
either defined or extracted from
+a compressed archive during CAS initialization.</p>
+</div>
+<div class="section" id="troubleshooting">
+<h2>Troubleshooting<a class="headerlink"
href="#troubleshooting" title="Permalink to this
headline">¶</a></h2>
+<p>Some of the major problems that arise when using CAS usually boils down to some
+improper usage of the compression and archiving tools.</p>
+<p>When compressing a core which may need to be sent over the network to a CAS
server
+one of the proper ways to do so is:</p>
+<div class="highlight-python"><pre>$ tar cvjf vmcore.12345.tar.bz2
vmcore.12345</pre>
+</div>
+<p>Other various ways of compressing archive are as follows:</p>
+<div class="highlight-python"><pre>$ tar cvzf vmcore.tar.gz vmcore
+$ gzip vmcore
+$ bzip2 vmcore</pre>
+</div>
+<p><tt class="docutils literal"><span
class="pre">Note</span></tt>: please do not double compress or
CAS will fail.</p>
+<p>Another issue, which isn&#8217;t primarily a fault of CAS, are
+incomplete or corrupted cores. If either of these occur
+there is a chance that CAS will not be able to process
+the data needed to associate a debug kernel or do any
+sort of automated analysis. Unfortunately, there is not
+much that can be done to resolve these sort of issues
+other than verifying that the process which happens when
+a system coredump and when that dump reaches the
+system specified for retrieval is solid and are seeing
+no errors.</p>
+</div>
 </div>
 <div class="section" id="resources">
 <h1>Resources<a class="headerlink" href="#resources"
title="Permalink to this headline">¶</a></h1>
 <ul class="simple">
 <li><a class="reference external"
href="http://fedorahosted.org/cas">CAS Wiki</a></li>
+<li><a class="reference external"
href="https://fedorahosted.org/cas/wiki/CasFAQ">CAS FAQ</a></li>
 <li><a class="reference external"
href="https://fedorahosted.org/mailman/listinfo/cas">Mailing
list</a></li>
 <li><a class="reference external"
href="https://fedorahosted.org/releases/c/a/cas/">Upstream
releases</a></li>
 <li>Checkout latest from Git, <tt class="docutils literal"><span
class="pre">git</span> <span
class="pre">clone</span> <span
class="pre">git://git.fedorahosted.org/cas.git</span>&...
@@ -218,18 +342,20 @@ the core.</p>
         <div class="sphinxsidebarwrapper">
             <h3><a href="">Table Of Contents</a></h3>
             <ul>
-<li><a class="reference external" href="">Core Analysis
System (CAS)</a><ul>
+<li><a class="reference external" href="">Core Analysis
System</a><ul>
 <li><a class="reference external"
href="#introduction">Introduction</a><ul>
 <li><a class="reference external"
href="#description">Description</a></li>
 <li><a class="reference external"
href="#prerequisites">Prerequisites</a></li>
 <li><a class="reference external"
href="#configuration">Configuration</a></li>
 </ul>
 </li>
-<li><a class="reference external"
href="#setup">Setup</a><ul>
+<li><a class="reference external"
href="#setup-execution">Setup &amp; Execution</a><ul>
 <li><a class="reference external"
href="#preparing-cas-server">Preparing CAS Server</a></li>
 <li><a class="reference external"
href="#running-cas">Running CAS</a></li>
 </ul>
 </li>
+<li><a class="reference external"
href="#analyzing">Analyzing</a></li>
+<li><a class="reference external"
href="#troubleshooting">Troubleshooting</a></li>
 </ul>
 </li>
 <li><a class="reference external"
href="#resources">Resources</a></li>
diff --git a/doc/searchindex.js b/doc/searchindex.js
index 6096119..5fd6ed0 100644
--- a/doc/searchindex.js
+++ b/doc/searchindex.js
@@ -1 +1 @@
-Search.setIndex({desctypes:{},terms:{all:0,identifi:0,help:0,execut:0,show:0,text:0,mnt:0,workdirectori:0,i386:0,abil:0,heavili:0,hierarchi:0,follow:0,disk:0,find:0,paramet:0,content:0,onli:0,samba:0,locat:0,system:0,kernel:0,also:0,configur:0,solut:0,specif:0,should:0,other:0,analyz:0,mail:0,tell:0,main:0,local:0,worth:0,match:0,depend:0,opt:0,crash:0,variou:0,python:0,timestamp:0,overal:0,initi:0,"break":0,mention:0,vmcore:0,upstream:0,ticket:0,now:0,relev:0,requir:0,introduct:0,like:0,organ:0,level:0,edit:0,list:0,authent:0,server:0,easili:0,necessari:0,either:0,have:0,contain:0,debug:0,output:0,architectur:0,where:0,mount:0,mean:0,wiki:0,x86_64:0,set:0,dump:0,some:0,direct:0,emac:0,result:0,pass:0,download:0,further:0,extract:0,tmp:0,shown:0,detect:0,mailserv:0,collect:0,databas:0,section:0,access:0,version:0,listinfo:[],debuglevel:0,determin:0,email:0,machin:0,core:0,assumpt:0,run:0,advanc:0,gener:0,each:0,usag:0,given:0,here:0,job:0,base:0,prerequisit:0,address:0,releas:0,org:0,come:0,sinc:0,valu:0,popul:0,sub:0,last:0,"500gb":0,admin:0,current:0,http:[],keep:0,vmlinux:0,etc:0,instanc:0,yum:0,includ:0,mani:0,typic:0,com:0,assign:0,first:0,load:0,rang:0,via:0,simpli:0,repositori:0,primarili:0,point:0,onc:0,modul:0,within:0,prefer:0,number:0,automat:0,crash_32:0,down:0,filenam:0,instruct:0,least:0,path:0,instal:0,next:0,storag:0,size:0,differ:0,git:0,mailman:[],describ:0,would:0,area:0,associ:0,question:0,two:0,messag:0,mark:0,avail:0,few:0,editor:0,rpm:0,recommend:0,hassl:0,addit:0,type:0,"final":0,store:0,rhel:0,files:0,media:0,from:0,properli:0,option:0,name:0,debuginfo:0,smtp:0,suit:0,thei:0,specifi:0,ani:0,administr:0,"var":0,"1tb":0,func:0,exactli:0,analyst:0,those:0,must:0,info:0,made:0,look:0,hous:0,provid:0,checkout:0,setup:0,work:0,uniqu:0,alter:0,defin:0,below:0,can:0,abov:0,visit:0,quickli:0,root:0,epel:0,timefram:0,later:0,conf:0,process:0,certain:0,dure:0,arg:0,share:0,anywher:0,accept:0,packag:0,exit:0,exist:0,uncom:0,file:0,need:0,fedorahost:0,sever:0,fill:0,queue:0,multipl:0,form:0,want:0,thing:0,suggest:0,user:0,when:0,same:0,note:0,how:0,valid:0,statement:0,build:0,which:0,command:0,eventu:0,prepar:0,enabl:0,analysi:0,therefor:0,express:0,resourc:0,x86:0,corefil:0,clone:0,who:0,what:0,reflect:0,most:0,regular:0,temporari:0,log:0,deploi:0,usr:0,data:0,fedora:0,repo:0,task:0,essenti:0,binari:0,filesystem:0,directori:0,gather:0,descript:0,issu:0,inform:0,exampl:0,environ:0,place:0,thi:0,anoth:0,rpmfilter:0,order:0,latest:0},titles:["Core
Analysis System (CAS)"],modules:{},descrefs:{},filenames:["index"]})
\ No newline at end of file
+Search.setIndex({desctypes:{},terms:{all:0,mnt:0,snip:0,abil:0,follow:0,disk:0,depend:0,do_dlm_lock:0,those:0,aris:0,worth:0,sent:0,r14:0,r15:0,r12:0,r13:0,r10:0,r11:0,faq:0,ffffffff8010e789:0,vmcore:0,upstream:0,ticket:0,relev:0,administr:0,level:0,die:0,list:0,setup:0,pleas:0,x86_64:0,intial:0,direct:0,pass:0,download:0,further:0,what:0,sub:0,section:0,abl:0,access:0,version:0,autogener:0,gener:0,here:0,address:0,path:0,sinc:0,valu:0,ffffffff80110bf5:0,rdx:0,queue:0,typic:0,rdi:0,smp_call_function_interrupt:0,chanc:0,"0000010001073f48":0,via:0,repositori:0,modul:0,prefer:0,crash_32:0,filenam:0,instal:0,feb:0,describ:0,would:0,prove:0,doubl:0,visit:0,two:0,next:0,few:0,rhel:0,recommend:0,type:0,tell:0,more:0,sort:0,wrapper:0,smtp:0,ffffffff803e9b80:0,ffffffff8010e81c:0,must:0,retriev:0,hous:0,prepar:0,work:0,uniqu:0,can:0,root:0,tar:0,process:0,share:0,accept:0,want:0,occur:0,multipl:0,anoth:0,how:0,error_exit:0,anyon:0,verifi:0,perspect:0,ffffffff80528000:0,resourc:0,"00000102000a4780":0,clone:0,reflect:0,mai:0,data:0,fedora:0,essenti:0,issu:0,inform:0,environ:0,media:0,order:0,help:0,over:0,major:0,i386:0,hierarchi:0,paramet:0,"100f57cb030":0,ellargesmp:0,bin:0,mail:0,main:0,alter:0,crash:0,than:0,python:0,timestamp:0,overal:0,initi:0,number:0,"break":0,mention:0,now:0,introduct:0,name:0,edit:0,troubleshoot:0,authent:0,easili:0,each:0,debug:0,mean:0,continu:0,happen:0,extract:0,out:0,shown:0,network:0,ffffffff8014cc1d:0,ffffffff8011d191:0,content:0,fffffffffffffffa:0,advanc:0,orig_rax:0,given:0,base:0,releas:0,org:0,ffffffff80110e1d:0,keep:0,vmlinux:0,thing:0,yum:0,isn:0,assign:0,first:0,origin:0,rang:0,redhat:0,onc:0,debuglevel:0,swapper:0,instruct:0,done:0,least:0,rflag:0,size:0,differ:0,script:0,associ:0,system:0,messag:0,ffffffff80112058:0,statement:0,ffffffff8047a0a0:0,"final":0,boil:0,editor:0,option:0,debuginfo:0,tool:0,specifi:0,"var":0,exactli:0,rsp:0,corefil:0,provid:0,remov:0,emac:0,structur:0,store:0,analysi:0,anywher:0,packag:0,have:0,call_function_interrupt:0,"101f3658030":0,rax:0,rsi:0,date:0,bz2:0,lib:0,note:0,also:0,build:0,which:0,begin:0,normal:0,previou:0,compress:0,most:0,regular:0,deploi:0,everyth:0,"101f21efb80":0,gather:0,place:0,determin:0,irq:0,latest:0,show:0,text:0,find:0,redirect:0,current:0,onli:0,locat:0,configur:0,solut:0,state:0,should:0,analyz:0,local:0,variou:0,cvjf:0,express:0,autom:0,repo:0,requir:0,enabl:0,organ:0,contain:0,where:0,wiki:0,kernel:0,set:0,dump:0,"10001073f48":0,see:0,result:0,arg:0,corrupt:0,subject:0,ffffffffa03183ff:0,detect:0,databas:0,someth:0,enough:0,listinfo:[],approach:0,email:0,altern:0,assumpt:0,cpu_idl:0,default_idl:0,job:0,come:0,addit:0,last:0,admin:0,fault:0,etc:0,instanc:0,mani:0,com:0,improp:0,load:0,simpli:0,point:0,"1000107bfb0":0,rpm:0,mailman:[],coredump:0,"101f21efb50":0,mark:0,much:0,popul:0,quickli:0,wish:0,ani:0,try_crashdump:0,"0000000000000e86":0,func:0,present:0,therefor:0,look:0,rbx:0,solid:0,mount:0,rbp:0,defin:0,abov:0,error:0,"101f21efb20":0,ffffffff8047a0b0:0,timefram:0,rip:0,need:0,archiv:0,uncom:0,conf:0,fedorahost:0,sever:0,thei:0,suggest:0,same:0,binari:0,eventu:0,http:[],x86:0,temporari:0,user:0,"500gb":0,engin:0,stack:0,gss:0,task:0,"10001073e98":0,do_invalid_op:0,exampl:0,command:0,thi:0,filesystem:0,gzip:0,fail:0,usual:0,identifi:0,execut:0,workdirectori:0,heavili:0,previous:0,samba:0,wed:0,except:0,other:0,match:0,opt:0,read:0,mod:0,"1000107bfa0":0,like:0,specif:0,manual:0,resolv:0,server:0,collect:0,necessari:0,either:0,"101f21efb60":0,"101f21efc40":0,output:0,some:0,gfs_quotad:0,proper:0,tmp:0,mailserv:0,assum:0,ffffffff80529f08:0,exit:0,machin:0,core:0,who:0,run:0,reach:0,usag:0,prerequisit:0,from:0,unfortun:0,primarili:0,within:0,automat:0,down:0,chang:0,start_disk_dump:0,storag:0,git:0,rcx:0,log:0,wai:0,area:0,support:0,question:0,avail:0,includ:0,suit:0,hassl:0,usr:0,files:0,properli:0,form:0,pwd:0,line:0,analyst:0,info:0,made:0,possibl:0,checkout:0,below:0,ffffffff80111c90:0,problem:0,similar:0,epel:0,later:0,certain:0,dure:0,pid:0,incomplet:0,exist:0,file:0,cvzf:0,fill:0,bzip2:0,"00000100f57cb030":0,when:0,valid:0,test:0,ffffffff8010e7a9:0,architectur:0,benefici:0,ffffffff80529fb8:0,directori:0,descript:0,"1tb":0,rpmfilter:0,cpu:0},titles:["Core
Analysis System"],modules:{},descrefs:{},filenames:["index"]})
\ No newline at end of file