<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SGLX A.12.80 TimeOut for cmrunpkg when second node failed. in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/sglx-a-12-80-timeout-for-cmrunpkg-when-second-node-failed/m-p/7177363#M57017</link>
    <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;We are faced with longtime timeout during package starting. What happens:&lt;BR /&gt;1. Package failed on the node without restart on second node. First node was gone off and unreachable.&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. We are trying start package to second node, but command cmrunpkg hung too long - no any messages in the package log file or system journal.&amp;nbsp; We can not wait more than 5 minutes and restarting second node.&lt;/P&gt;&lt;P&gt;3. After restarting second node we can run singlenode cluster via command cmruncl -f -n node2.&amp;nbsp; Package autostarted too.&lt;/P&gt;&lt;P&gt;Question - Why command cmrunpkg hung when one node of 2-nodes cluster is unreachable?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additional info:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We have tested and confirmed the behavior of the cluster node during the period when the second node is unavailable.&lt;/P&gt;&lt;P&gt;Test-case&lt;BR /&gt;Cluster has two node and one package - node1 and node2&lt;BR /&gt;We should stop testpkg&lt;BR /&gt;We should stop node node2 with poweroff&lt;BR /&gt;We should check deadman (lsof |grep deadman)&lt;BR /&gt;We should start testpkg on the running node&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Short results (timelapse)&lt;/P&gt;&lt;P&gt;Normal time for move package&lt;BR /&gt;date &amp;amp;&amp;amp; cmhaltpkg testpkg &amp;amp;&amp;amp; cmrunpkg -n node1 testpkg &amp;amp;&amp;amp; date ##Fri Nov 11 12:49:09 UTC 2022 - Fri Nov 11 12:50:22 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; cmhaltpkg testpkg &amp;amp;&amp;amp; cmrunpkg -n node2 testpkg &amp;amp;&amp;amp; date ##Fri Nov 11 12:51:15 UTC 2022 - Fri Nov 11 12:52:12 UTC 2022&lt;/P&gt;&lt;P&gt;Not Normal time&lt;BR /&gt;date &amp;amp;&amp;amp; cmviewcl ##Fri Nov 11 12:56:31 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; cmhaltpkg testpkg ##Fri Nov 11 12:56:40 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; poweroff ##Fri Nov 11 12:57:07 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; cmviewcl ##Fri Nov 11 12:57:20 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; lsof |grep deadman ##Fri Nov 11 12:57:29 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; tail -500 /var/log/messages | grep cmcld ##Fri Nov 11 12:57:37 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; time cmrunpkg testpkg ##Fri Nov 11 12:58:27 UTC 2022 - waiting 18 minutes and abort it&lt;BR /&gt;date &amp;amp;&amp;amp; cmhaltnode -f &amp;amp;&amp;amp; date ##Fri Nov 11 13:17:41 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; cmruncl -f -n node1 &amp;amp;&amp;amp; date ##Fri Nov 11 13:18:59 UTC 2022&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone encountered a similar situation?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 30 Nov 2022 05:45:26 GMT</pubDate>
    <dc:creator>yilmazaydin</dc:creator>
    <dc:date>2022-11-30T05:45:26Z</dc:date>
    <item>
      <title>SGLX A.12.80 TimeOut for cmrunpkg when second node failed.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sglx-a-12-80-timeout-for-cmrunpkg-when-second-node-failed/m-p/7177363#M57017</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;We are faced with longtime timeout during package starting. What happens:&lt;BR /&gt;1. Package failed on the node without restart on second node. First node was gone off and unreachable.&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. We are trying start package to second node, but command cmrunpkg hung too long - no any messages in the package log file or system journal.&amp;nbsp; We can not wait more than 5 minutes and restarting second node.&lt;/P&gt;&lt;P&gt;3. After restarting second node we can run singlenode cluster via command cmruncl -f -n node2.&amp;nbsp; Package autostarted too.&lt;/P&gt;&lt;P&gt;Question - Why command cmrunpkg hung when one node of 2-nodes cluster is unreachable?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additional info:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We have tested and confirmed the behavior of the cluster node during the period when the second node is unavailable.&lt;/P&gt;&lt;P&gt;Test-case&lt;BR /&gt;Cluster has two node and one package - node1 and node2&lt;BR /&gt;We should stop testpkg&lt;BR /&gt;We should stop node node2 with poweroff&lt;BR /&gt;We should check deadman (lsof |grep deadman)&lt;BR /&gt;We should start testpkg on the running node&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Short results (timelapse)&lt;/P&gt;&lt;P&gt;Normal time for move package&lt;BR /&gt;date &amp;amp;&amp;amp; cmhaltpkg testpkg &amp;amp;&amp;amp; cmrunpkg -n node1 testpkg &amp;amp;&amp;amp; date ##Fri Nov 11 12:49:09 UTC 2022 - Fri Nov 11 12:50:22 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; cmhaltpkg testpkg &amp;amp;&amp;amp; cmrunpkg -n node2 testpkg &amp;amp;&amp;amp; date ##Fri Nov 11 12:51:15 UTC 2022 - Fri Nov 11 12:52:12 UTC 2022&lt;/P&gt;&lt;P&gt;Not Normal time&lt;BR /&gt;date &amp;amp;&amp;amp; cmviewcl ##Fri Nov 11 12:56:31 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; cmhaltpkg testpkg ##Fri Nov 11 12:56:40 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; poweroff ##Fri Nov 11 12:57:07 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; cmviewcl ##Fri Nov 11 12:57:20 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; lsof |grep deadman ##Fri Nov 11 12:57:29 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; tail -500 /var/log/messages | grep cmcld ##Fri Nov 11 12:57:37 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; time cmrunpkg testpkg ##Fri Nov 11 12:58:27 UTC 2022 - waiting 18 minutes and abort it&lt;BR /&gt;date &amp;amp;&amp;amp; cmhaltnode -f &amp;amp;&amp;amp; date ##Fri Nov 11 13:17:41 UTC 2022&lt;BR /&gt;date &amp;amp;&amp;amp; cmruncl -f -n node1 &amp;amp;&amp;amp; date ##Fri Nov 11 13:18:59 UTC 2022&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone encountered a similar situation?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Nov 2022 05:45:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sglx-a-12-80-timeout-for-cmrunpkg-when-second-node-failed/m-p/7177363#M57017</guid>
      <dc:creator>yilmazaydin</dc:creator>
      <dc:date>2022-11-30T05:45:26Z</dc:date>
    </item>
    <item>
      <title>Re: SGLX A.12.80 TimeOut for cmrunpkg when second node failed.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sglx-a-12-80-timeout-for-cmrunpkg-when-second-node-failed/m-p/7177683#M57018</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;You are hitting a known problem which should be fixed in the next patch release(not sure on ETA). Please reach out to the support team for any workaround.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 05:45:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sglx-a-12-80-timeout-for-cmrunpkg-when-second-node-failed/m-p/7177683#M57018</guid>
      <dc:creator>Sush_S</dc:creator>
      <dc:date>2022-11-16T05:45:49Z</dc:date>
    </item>
  </channel>
</rss>

