<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>KB-1655 How to extract engine infrastructure logs from Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>KB-1655 How to extract engine infrastructure logs from Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments</link><pubDate>Thu, 23 Apr 2020 00:14:01 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Current Revision posted to Appian Knowledge Base by Parmida Borhani on 4/23/2020 12:14:01 AM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of certain log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract&amp;nbsp;these logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;h3&gt;18.3 and Later&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;Run the&amp;nbsp;&lt;/span&gt;&lt;a class="external-link" title="Follow link" href="https://docs.appian.com/suite/help/latest/Log_Collection_Script.html" rel="nofollow noopener noreferrer" target="_blank"&gt;log collection script&lt;/a&gt;&lt;span&gt;&amp;nbsp;to auto-generate the required&amp;nbsp;&lt;/span&gt;&lt;b&gt;.tar&lt;/b&gt;&lt;span&gt;&amp;nbsp;file.&lt;/span&gt;&lt;/p&gt;
&lt;h3&gt;18.2 and Earlier&lt;/h3&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory and then create the &lt;strong&gt;.tar&lt;/strong&gt; file.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;This is a multi-line command.&lt;/p&gt;
&lt;pre&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;br /&gt;find . \( \&lt;br /&gt;-name engine_status.csv \&lt;br /&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;br /&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;br /&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;gzip -f /tmp/${tarname}.tar&lt;/pre&gt;
&lt;p&gt;After running the command, upload the &lt;strong&gt;.tar&lt;/strong&gt; file to the support case as requested by Appian Support. These logs do not contain any personally identifiable information (PII).&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running 17.3 or later using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: April 2020&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: self-managed, logging, administration, linux, how-to, scripts, logs&lt;/div&gt;
</description></item><item><title>KB-1655 How to extract engine infrastructure logs from Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/27</link><pubDate>Fri, 17 Aug 2018 03:21:03 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 27 posted to Appian Knowledge Base by Parmida Borhani on 8/17/2018 3:21:03 AM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of certain log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract&amp;nbsp;these logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory and then create the &lt;strong&gt;.tar&lt;/strong&gt; file.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;This is a multi-line command.&lt;/p&gt;
&lt;pre&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;br /&gt;find . \( \&lt;br /&gt;-name engine_status.csv \&lt;br /&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;br /&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;br /&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;gzip -f /tmp/${tarname}.tar&lt;/pre&gt;
&lt;p&gt;After running the command, upload the &lt;strong&gt;.tar&lt;/strong&gt; file to the support case as requested by Appian Support. These logs do not contain any personally identifiable information (PII).&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running 17.3 or later using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: August 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, administration, linux, how-to, on-premise, logs&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract engine infrastructure logs from Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/26</link><pubDate>Tue, 14 Aug 2018 23:40:17 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 26 posted to Appian Knowledge Base by Parmida Borhani on 8/14/2018 11:40:17 PM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of certain log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract&amp;nbsp;these logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory and then create the &lt;strong&gt;.tar&lt;/strong&gt; file.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;This is a multi-line command.&lt;/p&gt;
&lt;pre&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;br /&gt;find . \( \&lt;br /&gt;-name engine_status.csv \&lt;br /&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;br /&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;br /&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;gzip -f /tmp/${tarname}.tar&lt;/pre&gt;
&lt;p&gt;After running the command, upload the &lt;strong&gt;.tar&lt;/strong&gt; file to the support case as requested by Appian Support. These logs do not contain any personally identifiable information (PII).&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running 17.3 or later using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: August 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, administration, linux, how-to, on-premise, logs&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/25</link><pubDate>Wed, 08 Aug 2018 21:41:13 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 25 posted to Appian Knowledge Base by Parmida Borhani on 8/8/2018 9:41:13 PM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of slim log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory and then create the &lt;strong&gt;.tar&lt;/strong&gt; file.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;This is a multi-line command.&lt;/p&gt;
&lt;pre&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;br /&gt;find . \( \&lt;br /&gt;-name engine_status.csv \&lt;br /&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;br /&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;br /&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;gzip -f /tmp/${tarname}.tar&lt;/pre&gt;
&lt;p&gt;After running the command, upload the &lt;strong&gt;.tar&lt;/strong&gt; file to the support case as requested by Appian Support. These logs do not contain any personally identifiable information (PII).&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running 17.3 or later using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: August 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, administration, linux, how-to, on-premise, logs&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/24</link><pubDate>Wed, 08 Aug 2018 21:39:38 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 24 posted to Appian Knowledge Base by Parmida Borhani on 8/8/2018 9:39:38 PM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of slim log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory and then create the &lt;strong&gt;.tar&lt;/strong&gt; file.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;This is a multi-line command.&lt;/p&gt;
&lt;pre&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;br /&gt;find . \( \&lt;br /&gt;-name engine_status.csv \&lt;br /&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;br /&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;br /&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;gzip -f /tmp/${tarname}.tar&lt;/pre&gt;
&lt;p&gt;After running the command, upload the &lt;strong&gt;.tar&lt;/strong&gt; file to the support case as requested by Appian Support. These logs do not contain any personally identifiable information (PII).&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running 17.3 or later using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: August 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/23</link><pubDate>Wed, 08 Aug 2018 11:51:43 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 23 posted to Appian Knowledge Base by Iram Khan on 8/8/2018 11:51:43 AM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of slim log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory and then create the &lt;strong&gt;.tar&lt;/strong&gt; file.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;this is a multi-line command.&lt;/p&gt;
&lt;pre&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;br /&gt;find . \( \&lt;br /&gt;-name engine_status.csv \&lt;br /&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;br /&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;br /&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;gzip -f /tmp/${tarname}.tar&lt;/pre&gt;
&lt;p&gt;After running the command, upload the &lt;strong&gt;.tar&lt;/strong&gt; file to the support case as requested by Appian Support.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running 17.3 or later using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: July 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/22</link><pubDate>Wed, 08 Aug 2018 11:32:15 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 22 posted to Appian Knowledge Base by Iram Khan on 8/8/2018 11:32:15 AM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of slim log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;this is a multi-line command.&lt;/p&gt;
&lt;pre&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;br /&gt;find . \( \&lt;br /&gt;-name engine_status.csv \&lt;br /&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;br /&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;br /&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;gzip -f /tmp/${tarname}.tar&lt;/pre&gt;
&lt;p&gt;After running the command, zip the logs in the &lt;code&gt;/tmp/&lt;/code&gt;&amp;nbsp;directory and upload it to the support case as requested by Appian Support.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running 17.3 or later using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: July 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/21</link><pubDate>Wed, 08 Aug 2018 11:27:21 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 21 posted to Appian Knowledge Base by Iram Khan on 8/8/2018 11:27:21 AM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of slim log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory. These files will be about 200 MB in size.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;this is a multi-line command.&lt;/p&gt;
&lt;pre&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;br /&gt;find . \( \&lt;br /&gt;-name engine_status.csv \&lt;br /&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;br /&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;br /&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;gzip -f /tmp/${tarname}.tar&lt;/pre&gt;
&lt;p&gt;After running the command, zip the logs in the &lt;code&gt;/tmp/&lt;/code&gt;&amp;nbsp;directory and upload it to the support case as requested by Appian Support.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running 17.3 or later using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: July 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/20</link><pubDate>Wed, 08 Aug 2018 11:20:36 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 20 posted to Appian Knowledge Base by Iram Khan on 8/8/2018 11:20:36 AM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of slim log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory. These files will be about 200MB in size.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;this is a multi-line command.&lt;/p&gt;
&lt;pre&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;br /&gt;find . \( \&lt;br /&gt;-name engine_status.csv \&lt;br /&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;br /&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;br /&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;gzip -f /tmp/${tarname}.tar&lt;/pre&gt;
&lt;p&gt;After running the command, zip the logs in the &lt;code&gt;/tmp/&lt;/code&gt;&amp;nbsp;directory and upload it to the support case as requested by Appian Support.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running 17.3 or later using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: July 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/19</link><pubDate>Wed, 08 Aug 2018 11:19:17 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 19 posted to Appian Knowledge Base by Iram Khan on 8/8/2018 11:19:17 AM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of slim log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory. These files will be about 200MB in size.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;this is a multi-line command.&lt;/p&gt;
&lt;pre&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;br /&gt;find . \( \&lt;br /&gt;-name engine_status.csv \&lt;br /&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;br /&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;br /&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;gzip -f /tmp/${tarname}.tar&lt;/pre&gt;
&lt;p&gt;After running the command, zip the logs in the &lt;code&gt;/tmp/&lt;/code&gt;&amp;nbsp;directory and upload it to the support case as requested by Appian Support.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running 17.3+ using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: July 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/18</link><pubDate>Wed, 08 Aug 2018 11:10:35 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 18 posted to Appian Knowledge Base by Iram Khan on 8/8/2018 11:10:35 AM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of slim log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory. These files be about 200MB in size.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;this is a multi-line command.&lt;/p&gt;
&lt;pre&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;br /&gt;find . \( \&lt;br /&gt;-name engine_status.csv \&lt;br /&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;br /&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;br /&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;gzip -f /tmp/${tarname}.tar&lt;/pre&gt;
&lt;p&gt;After running the command, zip the logs in the &lt;code&gt;/tmp/&lt;/code&gt;&amp;nbsp;directory and upload it to the support case as requested by Appian Support.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to versions of Appian 17.3 and later using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: July 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/17</link><pubDate>Fri, 13 Jul 2018 12:58:43 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Jordan Horwat</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 17 posted to Appian Knowledge Base by Jordan Horwat on 7/13/2018 12:58:43 PM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of slim log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory. These files be about 200MB in size.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;this is a multi-line command.&lt;/p&gt;
&lt;pre&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;br /&gt;find . \( \&lt;br /&gt;-name engine_status.csv \&lt;br /&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;br /&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;br /&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;br /&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;br /&gt;gzip -f /tmp/${tarname}.tar&lt;/pre&gt;
&lt;p&gt;After running the command, zip the logs in the &lt;code&gt;/tmp/&lt;/code&gt;&amp;nbsp;directory and upload it to the support case as requested by Appian Support.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: July 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/16</link><pubDate>Fri, 13 Jul 2018 12:57:43 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Jordan Horwat</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 16 posted to Appian Knowledge Base by Jordan Horwat on 7/13/2018 12:57:43 PM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of slim log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory. These files be about 200MB in size.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;this is a multi-line command.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find . \( \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-name engine_status.csv \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;gzip -f /tmp/${tarname}.tar&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;After running the command, zip the logs in the &lt;code&gt;/tmp/&lt;/code&gt;&amp;nbsp;directory and upload it to the support case as requested by Appian Support.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: July 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/15</link><pubDate>Fri, 13 Jul 2018 12:38:50 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 15 posted to Appian Knowledge Base by Iram Khan on 7/13/2018 12:38:50 PM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of slim log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory. These files be about 200MB in size.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;this is a multi-line command.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find . \( \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-name engine_status.csv \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;gzip -f /tmp/${tarname}.tar&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;After running the command, zip the logs in the &lt;code&gt;/tmp&lt;/code&gt; directory and upload it to the support case as requested by Appian Support.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: July 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/14</link><pubDate>Fri, 13 Jul 2018 10:18:37 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 14 posted to Appian Knowledge Base by Iram Khan on 7/13/2018 10:18:37 AM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;In order to assist with troubleshooting issues, Appian support cases&amp;nbsp;may require&amp;nbsp;the collection of slim log files from a specific Appian environment. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from&amp;nbsp;the&amp;nbsp;&lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in the &lt;code&gt;/tmp/&lt;/code&gt; directory. These files be about 200MB in size.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;&amp;nbsp;this is a multi-line command.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find . \( \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-name engine_status.csv \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;gzip -f /tmp/${tarname}.tar&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;After running the command, zip the logs in the &lt;code&gt;/tmp&lt;/code&gt; directory and upload it to the support case as requested by Appian Support.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian using Linux as the operating system.&lt;/p&gt;
&lt;p&gt;Last Reviewed: July 2018&lt;/p&gt;
&lt;p&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/13</link><pubDate>Thu, 12 Jul 2018 06:13:38 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 13 posted to Appian Knowledge Base by Iram Khan on 7/12/2018 6:13:38 AM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;Appian Technical Support sometimes require customers to provide slim logs from their Linux environments. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from your &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in your &lt;code&gt;tmp&lt;/code&gt; directory ~200MB (note this is a multi line command).&lt;/p&gt;
&lt;p&gt;&lt;code&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find . \( \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-name engine_status.csv \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;gzip -f /tmp/${tarname}.tar&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Once this is created, please zip the logs in your &lt;code&gt;tmp&lt;/code&gt;&amp;nbsp;directory and upload it to the Support Case as requested by Appian Technical Support.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running on a Linux environment.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/12</link><pubDate>Thu, 12 Jul 2018 06:09:45 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 12 posted to Appian Knowledge Base by Iram Khan on 7/12/2018 6:09:45 AM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;Solution Engineering sometimes require customers to provide slim logs from their Linux environments. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from your &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in your &lt;code&gt;tmp&lt;/code&gt; directory ~200MB (note this is a multi line command).&lt;/p&gt;
&lt;p&gt;&lt;code&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find . \( \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-name engine_status.csv \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;gzip -f /tmp/${tarname}.tar&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Once this is created, please zip the logs in your &lt;code&gt;tmp&lt;/code&gt;&amp;nbsp;directory and upload it to the Support Case as requested by the Solution Engineer.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running on a Linux environment.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/11</link><pubDate>Thu, 12 Jul 2018 06:09:00 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 11 posted to Appian Knowledge Base by Iram Khan on 7/12/2018 6:09:00 AM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;Solution Engineering sometimes require customers to provide slim logs from their Linux environments. This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from your &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in your &lt;code&gt;tmp&lt;/code&gt; directory ~200MB (note this is a multi line command).&lt;/p&gt;
&lt;p&gt;&lt;code&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find . \( \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-name engine_status.csv \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;gzip -f /tmp/${tarname}.tar&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;Once this is created, please zip the logs in your &lt;code&gt;tmp&lt;/code&gt;&amp;nbsp;directory and upload it to the Support Case as requested by the Solution Engineer.&lt;/code&gt;&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running on a Linux environment.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/10</link><pubDate>Tue, 10 Jul 2018 12:54:48 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 10 posted to Appian Knowledge Base by Iram Khan on 7/10/2018 12:54:48 PM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from your &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required &lt;strong&gt;.tar&lt;/strong&gt; file. This command will create a set of logs in your &lt;code&gt;tmp&lt;/code&gt; directory ~200MB (note this is a multi line command).&lt;/p&gt;
&lt;p&gt;&lt;code&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find . \( \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-name engine_status.csv \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;gzip -f /tmp/${tarname}.tar&lt;/code&gt;&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running on a Linux environment.&lt;/p&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;July 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/9</link><pubDate>Tue, 10 Jul 2018 12:51:20 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 9 posted to Appian Knowledge Base by Iram Khan on 7/10/2018 12:51:20 PM&lt;br /&gt;
&lt;h2&gt;Purpose&lt;/h2&gt;
&lt;p&gt;This article&amp;nbsp;provides instructions on&amp;nbsp;how to extract slim logs on Linux environments.&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;p&gt;Run the following command from your &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt; directory in order to generate the required .tar file. This command will create a set of logs in your &lt;code&gt;tmp&lt;/code&gt; directory ~200MB (note this is a multi line command).&lt;/p&gt;
&lt;p&gt;&lt;code&gt;tarname=$(hostname -s)-slim-$(date +&amp;quot;%Y-%m-%d&amp;quot;); \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find . \( \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-name engine_status.csv \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;*_summary.csv*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;service_manager*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;zookeeper*&amp;quot; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;ldquo;server.log&amp;rdquo; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;-o -name &amp;quot;product_metrics*&amp;quot; \) | tar -cvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./data-metrics/ | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/metrics/jvm | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;find ./service-manager/kafka | tar -rvf /tmp/${tarname}.tar --hard-dereference --files-from -; \&lt;/code&gt;&lt;br /&gt;&lt;code&gt;gzip -f /tmp/${tarname}.tar&lt;/code&gt;&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian running on a Linux environment.&lt;/p&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;July 2018&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item><item><title>How to extract slim logs on Linux environments</title><link>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments/revision/1</link><pubDate>Tue, 10 Jul 2018 12:48:15 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:84085ab5-3fbe-476f-b2d5-68a4a1da787c</guid><dc:creator>Iram Khan</dc:creator><comments>https://community.appian.com/support/w/kb/1023/kb-1655-how-to-extract-engine-infrastructure-logs-from-linux-environments#comments</comments><description>Revision 1 posted to Appian Knowledge Base by Iram Khan on 7/10/2018 12:48:15 PM&lt;br /&gt;
&lt;p&gt;Steps:&lt;/p&gt;
&lt;p&gt;Action:&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: logging, linux, how-to, on-premise, logs, SliM&lt;/div&gt;
</description></item></channel></rss>