<?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-2113 High Availability Service Manager cluster fails to shutdown</title><link>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>KB-2113 High Availability Service Manager cluster fails to shutdown</title><link>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown</link><pubDate>Tue, 12 May 2020 10:58:09 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6102c32a-b212-4f00-a702-ca38f62389b1</guid><dc:creator>James Lee</dc:creator><comments>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown#comments</comments><description>Current Revision posted to Appian Knowledge Base by James Lee on 5/12/2020 10:58:09 AM&lt;br /&gt;
&lt;h2&gt;&lt;span&gt;Symptoms&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;While attempting to shutdown the engines in a&amp;nbsp;High Availability cluster, the service manager process&amp;nbsp;fails to respond to requests for shutdown via the &lt;code&gt;stop.bat (.sh)&lt;/code&gt;&amp;nbsp;script located in &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/bin/&lt;/code&gt;. This is also true when passing the &lt;a href="https://docs.appian.com/suite/help/latest/Stop_Script.html"&gt;-c option&lt;/a&gt; to the stop script. Engines on a particular node will also fail to promote from REPLICA to PRIMARY.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;span&gt;After the shutdown attempt,&amp;nbsp;every&amp;nbsp;&amp;quot;&lt;tt&gt;&amp;#39;shutdown-cluster&amp;#39; invoked&lt;/tt&gt;&amp;quot; message may be immediately followed by a &amp;quot;&lt;tt&gt;Cluster shutdown already in progress!&lt;/tt&gt;&amp;quot; message in the &lt;strong&gt;service_manager.log&lt;/strong&gt;&amp;nbsp;(located in &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt;). For example:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!&lt;/pre&gt;
&lt;h2&gt;&lt;span&gt;Cause&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;These symptoms indicate that service manager was in a &amp;quot;&lt;span style="font-family:inherit;"&gt;cluster-stopping&lt;/span&gt;&amp;quot; state prior to initiating the graceful shutdown. This can occur when a&amp;nbsp;service manager&amp;nbsp;cluster stop is initiated via the stop script, or if there was an issue with a previous cluster shutdown, and only the engines&amp;nbsp;were restarted.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Action&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This issue can be remediated by restarting service manager:&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/stop.sh -p &amp;lt;password&amp;gt; -s manager&lt;/tt&gt;&lt;/span&gt;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/start.sh -p &amp;lt;password&amp;gt; -s all&lt;/tt&gt;&lt;/span&gt;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;If issues still occur,&amp;nbsp;open a case with Appian Support and note to the case description that you are experiencing&amp;nbsp;behavior in line with this article.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Affected Versions&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This article applies to&amp;nbsp;Appian 18.1 and higher running in a High Availability Topology.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Last Reviewed:&amp;nbsp;May&amp;nbsp;2020&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: engines, infrastructure, service manager&lt;/div&gt;
</description></item><item><title>KB-XXXX High Availability Service Manager cluster refuses to shutdown</title><link>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown/revision/9</link><pubDate>Tue, 12 May 2020 10:56:26 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6102c32a-b212-4f00-a702-ca38f62389b1</guid><dc:creator>James Lee</dc:creator><comments>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown#comments</comments><description>Revision 9 posted to Appian Knowledge Base by James Lee on 5/12/2020 10:56:26 AM&lt;br /&gt;
&lt;h2&gt;&lt;span&gt;Symptoms&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;While attempting to shutdown the engines in a&amp;nbsp;High Availability cluster, the service manager process&amp;nbsp;fails to respond to requests for shutdown via the &lt;code&gt;stop.bat (.sh)&lt;/code&gt;&amp;nbsp;script located in &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/bin/&lt;/code&gt;. This is also true when passing the &lt;a href="https://docs.appian.com/suite/help/latest/Stop_Script.html"&gt;-c option&lt;/a&gt; to the stop script. Engines on a particular node will also fail to promote from REPLICA to PRIMARY.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;span&gt;After the shutdown attempt,&amp;nbsp;every&amp;nbsp;&amp;quot;&lt;tt&gt;&amp;#39;shutdown-cluster&amp;#39; invoked&lt;/tt&gt;&amp;quot; message may be immediately followed by a &amp;quot;&lt;tt&gt;Cluster shutdown already in progress!&lt;/tt&gt;&amp;quot; message in the &lt;strong&gt;service_manager.log&lt;/strong&gt;&amp;nbsp;(located in &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt;). For example:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!&lt;/pre&gt;
&lt;h2&gt;&lt;span&gt;Cause&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;These symptoms indicate that service manager was in a &amp;quot;&lt;span style="font-family:inherit;"&gt;cluster-stopping&lt;/span&gt;&amp;quot; state prior to initiating the graceful shutdown. This can occur when a&amp;nbsp;service manager&amp;nbsp;cluster stop is initiated via the stop script, or if there was an issue with a previous cluster shutdown, and only the engines&amp;nbsp;were restarted.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Action&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This issue can be remediated by restarting service manager:&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/stop.sh -p &amp;lt;password&amp;gt; -s manager&lt;/tt&gt;&lt;/span&gt;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/start.sh -p &amp;lt;password&amp;gt; -s all&lt;/tt&gt;&lt;/span&gt;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;If issues still occur,&amp;nbsp;open a case with Appian Support and note to the case description that you are experiencing&amp;nbsp;behavior in line with this article.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Affected Versions&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This article applies to&amp;nbsp;Appian 18.1 and higher running in a High Availability Topology.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Last Reviewed:&amp;nbsp;May&amp;nbsp;2020&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: engines, infrastructure, service manager&lt;/div&gt;
</description></item><item><title>KB-XXXX High Availability Service Manager cluster refuses to shutdown</title><link>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown/revision/8</link><pubDate>Mon, 11 May 2020 07:59:32 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6102c32a-b212-4f00-a702-ca38f62389b1</guid><dc:creator>Sean Kim</dc:creator><comments>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown#comments</comments><description>Revision 8 posted to Appian Knowledge Base by Sean Kim on 5/11/2020 7:59:32 AM&lt;br /&gt;
&lt;h2&gt;&lt;span&gt;Symptoms&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;While attempting to shutdown the engines in a&amp;nbsp;High Availability cluster, the service manager process&amp;nbsp;fails to respond to requests for shutdown via the &lt;code&gt;stop.bat (.sh)&lt;/code&gt;&amp;nbsp;script located in &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/bin/&lt;/code&gt;. This is also true when passing the &lt;a href="https://docs.appian.com/suite/help/latest/Stop_Script.html"&gt;-c option&lt;/a&gt; to the stop script. Engines on a particular node will also fail to promote from REPLICA to PRIMARY.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;span&gt;After the shutdown attempt,&amp;nbsp;every&amp;nbsp;&amp;quot;&lt;tt&gt;&amp;#39;shutdown-cluster&amp;#39; invoked&lt;/tt&gt;&amp;quot; message may be immediately followed by a &amp;quot;&lt;tt&gt;Cluster shutdown already in progress!&lt;/tt&gt;&amp;quot; message in the &lt;strong&gt;service_manager.log&lt;/strong&gt;&amp;nbsp;(located in &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/)&lt;/code&gt;. For example:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!&lt;/pre&gt;
&lt;h2&gt;&lt;span&gt;Cause&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;These symptoms indicate that service manager was in a &amp;quot;&lt;span style="font-family:inherit;"&gt;cluster-stopping&lt;/span&gt;&amp;quot; state prior to initiating the graceful shutdown. This can occur when a&amp;nbsp;service manager&amp;nbsp;cluster stop is initiated via the stop script, or if there was an issue with a previous cluster shutdown, and only the engines&amp;nbsp;were restarted.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Action&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This issue can be remediated by restarting service manager:&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/stop.sh -p &amp;lt;password&amp;gt; -s manager&lt;/tt&gt;&lt;/span&gt;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/start.sh -p &amp;lt;password&amp;gt; -s all&lt;/tt&gt;&lt;/span&gt;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;If issues still occur,&amp;nbsp;open a case with Appian Support and note to the case description that you are experiencing&amp;nbsp;behavior in line with this article.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Affected Versions&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This article applies to&amp;nbsp;Appian 18.1 and higher running in a High Availability Topology.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Last Reviewed:&amp;nbsp;May&amp;nbsp;2020&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: engines, infrastructure, service manager&lt;/div&gt;
</description></item><item><title>KB-XXXX High Availability Service Manager cluster refuses to shutdown</title><link>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown/revision/7</link><pubDate>Thu, 07 May 2020 13:37:48 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6102c32a-b212-4f00-a702-ca38f62389b1</guid><dc:creator>Philip Moss</dc:creator><comments>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown#comments</comments><description>Revision 7 posted to Appian Knowledge Base by Philip Moss on 5/7/2020 1:37:48 PM&lt;br /&gt;
&lt;h2&gt;&lt;span&gt;Symptoms&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;While attempting to shutdown the engines in a&amp;nbsp;High Availability cluster, the service manager process&amp;nbsp;fails to respond to requests for shutdown via the &lt;code&gt;stop.bat (.sh)&lt;/code&gt;&amp;nbsp;script located in &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/bin/&lt;/code&gt;. This is also true when passing the &lt;a href="https://docs.appian.com/suite/help/latest/Stop_Script.html"&gt;-c option&lt;/a&gt; to the stop script. Engines on a particular node will also fail to promote from REPLICA to PRIMARY.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;span&gt;After the shutdown attempt,&amp;nbsp;every&amp;nbsp;&amp;quot;&lt;tt&gt;&amp;#39;shutdown-cluster&amp;#39; invoked&lt;/tt&gt;&amp;quot; message may be immediately followed by a &amp;quot;&lt;tt&gt;Cluster shutdown already in progress!&lt;/tt&gt;&amp;quot; message in the &lt;strong&gt;service_manager.log&lt;/strong&gt;&amp;nbsp;(located in &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/)&lt;/code&gt;. For example:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!&lt;/pre&gt;
&lt;h2&gt;&lt;span&gt;Cause&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;These symptoms indicate that service manager was in a &amp;quot;&lt;span style="font-family:inherit;"&gt;cluster-stopping&lt;/span&gt;&amp;quot; state prior to initiating the graceful shutdown. This can occur when a&amp;nbsp;service manager&amp;nbsp;cluster stop is initiated via the stop script, or if there was an issue with a previous cluster shutdown, and only the engines&amp;nbsp;were restarted.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Action&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This issue can be remediated by restarting service manager:&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/stop.sh -p &amp;lt;password&amp;gt; -s manager&lt;/tt&gt;&lt;/span&gt;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/start.sh -p &amp;lt;password&amp;gt; -s all&lt;/tt&gt;&lt;/span&gt;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;If issues still occur,&amp;nbsp;open a case with Appian Support and note to the case description that you are experiencing&amp;nbsp;behavior in line with this article.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Affected Versions&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This article applies to all versions of Appian running Service Manager with a High Availability Topology.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Last Reviewed:&amp;nbsp;May&amp;nbsp;2020&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: engines, infrastructure, service manager&lt;/div&gt;
</description></item><item><title>KB-XXXX High Availability Service Manager cluster refuses to shutdown</title><link>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown/revision/6</link><pubDate>Wed, 06 May 2020 13:52:27 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6102c32a-b212-4f00-a702-ca38f62389b1</guid><dc:creator>James Lee</dc:creator><comments>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown#comments</comments><description>Revision 6 posted to Appian Knowledge Base by James Lee on 5/6/2020 1:52:27 PM&lt;br /&gt;
&lt;h2&gt;&lt;span&gt;Symptoms&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;While attempting to shutdown the engines in a&amp;nbsp;High Availability cluster, the service manager process&amp;nbsp;fails to respond to requests for shutdown via the &lt;code&gt;stop.bat (.sh)&lt;/code&gt;&amp;nbsp;script located in &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/bin/&lt;/code&gt;. This is also true when passing the &lt;a href="https://docs.appian.com/suite/help/latest/Stop_Script.html"&gt;-c option&lt;/a&gt; to the stop script. Engines on a particular node will also fail to promote from REPLICA to PRIMARY.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;T&lt;/span&gt;&lt;span&gt;he following message may print in the &lt;strong&gt;service_manager.log&lt;/strong&gt; located in &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/&lt;/code&gt;:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked&lt;/pre&gt;
&lt;p&gt;&lt;span&gt;Additionally,&amp;nbsp;every&amp;nbsp;&amp;quot;&lt;tt&gt;&amp;#39;shutdown-cluster&amp;#39; invoked&lt;/tt&gt;&amp;quot; message may be immediately followed by a &amp;quot;&lt;tt&gt;Cluster shutdown already in progress!&lt;/tt&gt;&amp;quot; message. For example:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!&lt;/pre&gt;
&lt;h2&gt;&lt;span&gt;Cause&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;These symptoms indicate that service manager was in a &amp;quot;&lt;span style="font-family:inherit;"&gt;cluster-stopping&lt;/span&gt;&amp;quot; state prior to initiating the graceful shutdown. This can occur when a&amp;nbsp;service manager&amp;nbsp;cluster stop is initiated via the stop script, or if there was an issue with a previous cluster shutdown, and only the engines&amp;nbsp;were restarted.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Action&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This issue can be remediated by restarting service manager:&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/stop.sh -p &amp;lt;password&amp;gt; -s manager&lt;/tt&gt;&lt;/span&gt;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/start.sh -p &amp;lt;password&amp;gt; -s all&lt;/tt&gt;&lt;/span&gt;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;If issues still occur,&amp;nbsp;open a case with Appian Support and note to the case description that you are experiencing&amp;nbsp;behavior in line with this article.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Affected Versions&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This article applies to all versions of Appian running Service Manager with a High Availability Topology.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Last Reviewed:&amp;nbsp;May&amp;nbsp;2020&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: engines, infrastructure, service manager&lt;/div&gt;
</description></item><item><title>KB-XXXX High Availability Service Manager cluster refuses to shutdown</title><link>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown/revision/4</link><pubDate>Mon, 04 May 2020 14:09:45 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6102c32a-b212-4f00-a702-ca38f62389b1</guid><dc:creator>Sean Kim</dc:creator><comments>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown#comments</comments><description>Revision 4 posted to Appian Knowledge Base by Sean Kim on 5/4/2020 2:09:45 PM&lt;br /&gt;
&lt;h2&gt;&lt;span&gt;Symptoms&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;While attempting to shutdown the engines in an HA cluster, the service manager process refuses to carry out the shutdown and ignores the stop script.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Users may see the following message in the service manager log:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked&lt;/pre&gt;
&lt;p&gt;&lt;span&gt;Additionally, Users may see that every &amp;quot;&lt;tt&gt;&amp;#39;shutdown-cluster&amp;#39; invoked&lt;/tt&gt;&amp;quot; message&amp;nbsp;is immediately followed by a &amp;quot;&lt;tt&gt;Cluster shutdown already in progress!&lt;/tt&gt;&amp;quot; message. For example:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:arial, helvetica, sans-serif;"&gt;&lt;span style="font-family:inherit;"&gt;However, the shutdown does not proceed as expected.&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/pre&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Summary of symptoms:&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Failed graceful shutdown for HA sites&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Service Manager is unresponsive to&amp;nbsp;the stop script, even with the -c option&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Engines fail to promote to PRIMARY on a particular node (even if there are no other primaries and the engine is a RUNNING REPLICA)&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;&lt;span&gt;Cause&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;These symptoms indicate that service manager was in a &amp;quot;&lt;span style="font-family:inherit;"&gt;cluster-stop&lt;/span&gt;&amp;quot; state prior to initiating the graceful shutdown. Typically, a user is trying to shutdown service manager on just one node in an HA configuration, but accidentally does a cluster stop which affects all other service managers in a cluster. Service manager could also get into this state if there was an issue with an intentional cluster shutdown, but only the engines are restarted and not service manager&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Action&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This issue can be remediated by restarting service manager by running the following:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/stop.sh -p XXXXXXX -s manager&lt;/tt&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/start.sh -p XXXXXXX -s all&lt;/tt&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If issues still occur, please contact Appian Support by creating a support case or emailing support@appian.com.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Affected Versions&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This article applies to all versions of Appian running with a High Availability Topology&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Last Reviewed:&amp;nbsp;May&amp;nbsp;2020&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: engines, service manager&lt;/div&gt;
</description></item><item><title>KB-XXXX High Availability Service Manager cluster refuses to shutdown</title><link>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown/revision/3</link><pubDate>Mon, 04 May 2020 14:07:49 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6102c32a-b212-4f00-a702-ca38f62389b1</guid><dc:creator>Sean Kim</dc:creator><comments>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown#comments</comments><description>Revision 3 posted to Appian Knowledge Base by Sean Kim on 5/4/2020 2:07:49 PM&lt;br /&gt;
&lt;h2&gt;&lt;span&gt;Symptoms&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;While attempting to shutdown the engines in an HA cluster, the service manager process refuses to carry out the shutdown and ignores the stop script.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Users may see the following message in the service manager log:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked&lt;/pre&gt;
&lt;p&gt;&lt;span&gt;Additionally, Users may see that every &amp;quot;&lt;tt&gt;&amp;#39;shutdown-cluster&amp;#39; invoked&lt;/tt&gt;&amp;quot; message&amp;nbsp;is immediately followed by a &amp;quot;&lt;tt&gt;Cluster shutdown already in progress!&lt;/tt&gt;&amp;quot; message. For example:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:arial, helvetica, sans-serif;"&gt;&lt;span style="font-family:inherit;"&gt;However, the shutdown does not proceed as expected.&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/pre&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Summary of symptoms:&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Failed graceful shutdown for HA sites&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Service Manager is unresponsive to&amp;nbsp;the stop script, even with the -c option&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Engines fail to promote to PRIMARY on a particular node (even if there are no other primaries and the engine is a RUNNING REPLICA)&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;&lt;span&gt;Cause&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;These symptoms indicate that service manager was in a &amp;quot;&lt;span style="font-family:inherit;"&gt;cluster-stop&lt;/span&gt;&amp;quot; state prior to initiating the graceful shutdown. Typically, a user is trying to shutdown service manager on just one node in an HA configuration, but accidentally does a cluster stop which affects all other service managers in a cluster. Service manager could also get into this state if there was an issue with an intentional cluster shutdown, but only the engines are restarted and not service manager&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Action&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This issue can be remediated by restarting service manager by running the following:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/stop.sh -p XXXXXXX -s manager&lt;/tt&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;tt&gt;&amp;lt;APPIAN_HOME&amp;gt;/services/start.sh -p XXXXXXX -s all&lt;/tt&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Affected Versions&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This article applies to all versions of Appian running with a High Availability Topology&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Last Reviewed:&amp;nbsp;May&amp;nbsp;2020&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: engines, service manager&lt;/div&gt;
</description></item><item><title>KB-XXXX High Availability Service Manager cluster refuses to shutdown</title><link>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown/revision/2</link><pubDate>Mon, 04 May 2020 13:29:49 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6102c32a-b212-4f00-a702-ca38f62389b1</guid><dc:creator>Philip Moss</dc:creator><comments>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown#comments</comments><description>Revision 2 posted to Appian Knowledge Base by Philip Moss on 5/4/2020 1:29:49 PM&lt;br /&gt;
&lt;h2&gt;&lt;span&gt;Symptoms&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;While attempting to shutdown the engines in an HA cluster, the service manager process refuses to carry out the shutdown and ignores the stop script.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Users may see the following message in the service manager log:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked&lt;/pre&gt;
&lt;p&gt;&lt;span&gt;Additionally, Users may see that every &amp;quot;&lt;tt&gt;&amp;#39;shutdown-cluster&amp;#39; invoked&lt;/tt&gt;&amp;quot; message&amp;nbsp;is immediately followed by a &amp;quot;&lt;tt&gt;Cluster shutdown already in progress!&lt;/tt&gt;&amp;quot; message. For example:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:arial, helvetica, sans-serif;"&gt;&lt;span style="font-family:inherit;"&gt;However, the shutdown does not proceed as expected.&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/pre&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Summary of symptoms:&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Failed graceful shutdown for HA sites&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Service Manager is unresponsive to&amp;nbsp;the stop script, even with the -c option&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Engines fail to promote to PRIMARY on a particular node (even if there are no other primaries and the engine is a RUNNING REPLICA)&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;&lt;span&gt;Cause&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;These symptoms indicate that service manager was in a &amp;quot;&lt;span style="font-family:inherit;"&gt;cluster-stop&lt;/span&gt;&amp;quot; state prior to initiating the graceful shutdown. Typically, a user is trying to shutdown service manager on just one node in an HA configuration, but accidentally does a cluster stop which affects all other service managers in a cluster. Service manager could also get into this state if there was an issue with an intentional cluster shutdown, but only the engines are restarted and not service manager&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Action&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This issue can be remediated by restarting service manager.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;&lt;/span&gt;&lt;/h2&gt;
&lt;h2&gt;&lt;span&gt;Affected Versions&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This article applies to all versions of Appian running with a High Availability Topology&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Last Reviewed:&amp;nbsp;May&amp;nbsp;2020&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: engines, service manager&lt;/div&gt;
</description></item><item><title>KB-XXXX High Availability Service Manager cluster refuses to shutdown</title><link>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown/revision/1</link><pubDate>Thu, 30 Apr 2020 13:35:06 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6102c32a-b212-4f00-a702-ca38f62389b1</guid><dc:creator>Sean Kim</dc:creator><comments>https://community.appian.com/support/w/kb/1782/kb-2113-high-availability-service-manager-cluster-fails-to-shutdown#comments</comments><description>Revision 1 posted to Appian Knowledge Base by Sean Kim on 4/30/2020 1:35:06 PM&lt;br /&gt;
&lt;h2&gt;&lt;span&gt;Symptoms&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;While attempting to shutdown the engines in an HA cluster, the service manager process refuses to carry out the shutdown and ignores the stop script.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Users may see the following message in the logs:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked&lt;/pre&gt;
&lt;p&gt;&lt;span&gt;However the shutdown does not proceed as expected.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Alternatively, if there was an issue with a graceful shutdown, the cluster-stop state is most likely the root cause if every &amp;quot;&lt;tt&gt;&amp;#39;shutdown-cluster&amp;#39; invoked&lt;/tt&gt;&amp;quot; message is immediately followed by a &amp;quot;&lt;tt&gt;Cluster shutdown already in progress!&lt;/tt&gt;&amp;quot; message in the SM log. For example:&lt;/span&gt;&lt;/p&gt;
&lt;pre class="code-java"&gt;INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Manager action &lt;span class="code-quote"&gt;&amp;#39;shutdown-cluster&amp;#39;&lt;/span&gt; invoked
INFO  com.appian.komodo.admin.route.ManagerActionsRoute - Cluster shutdown already in progress!&lt;/pre&gt;
&lt;p&gt;&lt;span&gt;Summary of symptoms:&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Failed graceful shutdown for HA sites&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Service Manager is unresponsive to&amp;nbsp;the stop script, even with the -c option.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Engines fail to promote to PRIMARY on a particular node (even if there are no other primaries and the engine is a RUNNING REPLICA)&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;&lt;span&gt;Cause&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;Typically, a user is trying to shutdown service manager on just one node in an HA configuration, but accidentally does a cluster stop which affects all other service managers in a cluster. SM could also get into this state if there is an issue with an intentional cluster shutdown, but only the engines are restarted and not service manager&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;Action&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This issue can be remediated by restarting service manager.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;&lt;span&gt;&lt;/span&gt;&lt;/h2&gt;
&lt;h2&gt;&lt;span&gt;Affected Versions&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;This article applies to all versions of Appian running with a High Availability Topology&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Last Reviewed:&amp;nbsp;May&amp;nbsp;2020&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: engines, service manager&lt;/div&gt;
</description></item></channel></rss>