<?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 Re: MC Service Guard Pakage Startup Hung in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard-pakage-startup-hung/m-p/2829173#M88441</link>
    <description>Hi,&lt;BR /&gt;     If halting the cluster is not a problem then just halt the clusters and then restart the cluster.  This should bring the package in the right state&lt;BR /&gt;&lt;BR /&gt;To forcefully halt cluster&lt;BR /&gt;cmhaltcl -f&lt;BR /&gt;&lt;BR /&gt;to start cluster&lt;BR /&gt;cmruncl&lt;BR /&gt;&lt;BR /&gt;  Sushil</description>
    <pubDate>Fri, 18 Oct 2002 19:58:12 GMT</pubDate>
    <dc:creator>Sushil Singh_1</dc:creator>
    <dc:date>2002-10-18T19:58:12Z</dc:date>
    <item>
      <title>MC Service Guard Pakage Startup Hung</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard-pakage-startup-hung/m-p/2829172#M88440</link>
      <description>When trying&lt;BR /&gt;cmrunpkg -v -n [node] [pakage] command&lt;BR /&gt;&lt;BR /&gt;It is unable to startup.  Reporting "starting" but never completes action. Even after package is attempted to hault. Trying to haut with cmhaltpkg.&lt;BR /&gt;&lt;BR /&gt;cmviewcl - is not coming out of the "starting" status.&lt;BR /&gt;&lt;BR /&gt;What command could I use to force a hault package other that cmviewcl -v?&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Oct 2002 19:47:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard-pakage-startup-hung/m-p/2829172#M88440</guid>
      <dc:creator>Tami Doyen</dc:creator>
      <dc:date>2002-10-18T19:47:36Z</dc:date>
    </item>
    <item>
      <title>Re: MC Service Guard Pakage Startup Hung</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard-pakage-startup-hung/m-p/2829173#M88441</link>
      <description>Hi,&lt;BR /&gt;     If halting the cluster is not a problem then just halt the clusters and then restart the cluster.  This should bring the package in the right state&lt;BR /&gt;&lt;BR /&gt;To forcefully halt cluster&lt;BR /&gt;cmhaltcl -f&lt;BR /&gt;&lt;BR /&gt;to start cluster&lt;BR /&gt;cmruncl&lt;BR /&gt;&lt;BR /&gt;  Sushil</description>
      <pubDate>Fri, 18 Oct 2002 19:58:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard-pakage-startup-hung/m-p/2829173#M88441</guid>
      <dc:creator>Sushil Singh_1</dc:creator>
      <dc:date>2002-10-18T19:58:12Z</dc:date>
    </item>
    <item>
      <title>Re: MC Service Guard Pakage Startup Hung</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard-pakage-startup-hung/m-p/2829174#M88442</link>
      <description>Hi Tami,&lt;BR /&gt;&lt;BR /&gt;You need to look at the log for that package - it's usually in &lt;BR /&gt;/etc/cmcluster/pkg_name/ &lt;BR /&gt;and should be the only log file in that dir.&lt;BR /&gt;You'll get a better idea of what happened during the start of the pkg.&lt;BR /&gt;&lt;BR /&gt;You can halt the pkg by determining what script(s) the pkg runs at start - again by looking at the pkg control file in &lt;BR /&gt;/etc/cmcluster/pkg_name&lt;BR /&gt;And looking for that script via&lt;BR /&gt;ps -ef | grep script_name&lt;BR /&gt;Then kill that process. One of two things will happen - either the pkg will move to halted OR started in a cmviewcl output.&lt;BR /&gt;If in started mode just cmhalt it.&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;Jeff</description>
      <pubDate>Fri, 18 Oct 2002 20:28:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-service-guard-pakage-startup-hung/m-p/2829174#M88442</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2002-10-18T20:28:32Z</dc:date>
    </item>
  </channel>
</rss>

