<?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: Node keeps crashing in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944951#M699656</link>
    <description>Hi Geoff,&lt;BR /&gt;&lt;BR /&gt;It seems that the test node had initiating the TOC of it own.&lt;BR /&gt;&lt;BR /&gt;I would just start the node using cmrunnod &lt;TEST-NODE&gt;. This is just to ensure the cluster service of the node work OK under the configured cluster enviornment.&lt;BR /&gt;Then the further debugging could be done at the package level i,e. cluster services , application startup and monitoring.&lt;BR /&gt; &lt;BR /&gt;I am just wondering about the line in syslog about cmmodnet . It maybe a case the command is not going through may be&lt;BR /&gt;hanged or something. I would very the package IP conflict.  Since the node was crashed before , it may be required&lt;BR /&gt;to clean up the pakcage IP using cmmodnet -r before starting the package.&lt;BR /&gt;&lt;BR /&gt;Did you check the /etc/shutdownlog on this node? &lt;BR /&gt;&lt;BR /&gt;You can check the SGFR as well using cmfmtfr &lt;BR /&gt;&lt;BR /&gt;&lt;/TEST-NODE&gt;</description>
    <pubDate>Tue, 06 Dec 2005 19:33:36 GMT</pubDate>
    <dc:creator>Sameer_Nirmal</dc:creator>
    <dc:date>2005-12-06T19:33:36Z</dc:date>
    <item>
      <title>Node keeps crashing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944948#M699653</link>
      <description>I have a call in with HP - but in the meantime I thought I'd share this with you.&lt;BR /&gt;&lt;BR /&gt;2 node cluster - one runs a prod db and the other test.&lt;BR /&gt;&lt;BR /&gt;The test crashed - for no apparent reason - other then this in the syslog of the prod node:&lt;BR /&gt;&lt;BR /&gt;Dec  6 13:09:24 svr3001 cmcld: New node svr3000 is joining the cluster&lt;BR /&gt;Dec  6 13:09:24 svr3001 cmcld: Attempting to adjust cluster membership&lt;BR /&gt;Dec  6 13:09:24 svr3001 cmcld: Beginning standard partial election&lt;BR /&gt;Dec  6 13:09:28 svr3001 cmcld: Enabling safety time protection&lt;BR /&gt;Dec  6 13:09:28 svr3001 cmcld: Clearing Cluster Lock&lt;BR /&gt;Dec  6 13:09:30 svr3001 cmcld: 2 nodes have formed a new cluster, sequence #18&lt;BR /&gt;Dec  6 13:09:30 svr3001 cmcld: The new active cluster membership is: svr3001(id=2), svr3000(id=1)&lt;BR /&gt;Dec  6 13:09:30 svr3001 cmcld: Package ilogtest cannot run on this node because switching has been disabled for this node&lt;BR /&gt;Dec  6 13:09:31 svr3001 cmcld: One or more packages is not currently running because AUTO_RUN is disabled so that it cannot start automatically. To start these packages, enable AUTO_RUN via cmmodpkg -e &lt;PACKAGE_NAME&gt;.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Dec  6 13:11:20 svr3001 cmcld: Timed out node svr3000. It may have failed.&lt;BR /&gt;Dec  6 13:11:20 svr3001 cmcld: Attempting to adjust cluster membership&lt;BR /&gt;Dec  6 13:11:20 svr3001 cmcld: Beginning standard partial election&lt;BR /&gt;Dec  6 13:11:22 svr3001 cmclconfd[13667]: Updated file /var/adm/cmcluster/frdump.cmcld.3 for node svr3001 (length = 512096).&lt;BR /&gt;Dec  6 13:11:30 svr3001 cmcld: Obtaining Cluster Lock&lt;BR /&gt;Dec  6 13:11:31 svr3001 cmcld: Turning off safety time protection since the cluster&lt;BR /&gt;Dec  6 13:11:31 svr3001 cmcld: may now consist of a single node.  If Serviceguard&lt;BR /&gt;Dec  6 13:11:31 svr3001 cmcld: fails, this node will not automatically halt&lt;BR /&gt;Dec  6 13:11:31 svr3001 cmcld: This will not affect the behavior of Package Failfast&lt;BR /&gt;Dec  6 13:11:31 svr3001 cmcld: or Service Failfast. If such a package or service fails,&lt;BR /&gt;Dec  6 13:11:31 svr3001 cmcld:  safety timer will be re-enabled and this node will&lt;BR /&gt;Dec  6 13:11:31 svr3001 cmcld:  automatically halt.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The server crashed (the first time) on it's own.&lt;BR /&gt;&lt;BR /&gt;Since then, everytime I try a cmrunpkg -n svr3000 packtst, it crashes.&lt;BR /&gt;&lt;BR /&gt;And the kicker - NO CRASHDUMP!&lt;BR /&gt;&lt;BR /&gt;/var/adm/crash is configured, as well as dump:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;# lvlnboot -v&lt;BR /&gt;Boot Definitions for Volume Group /dev/vg00:&lt;BR /&gt;Physical Volumes belonging in Root Volume Group:&lt;BR /&gt;        /dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk&lt;BR /&gt;        /dev/dsk/c2t2d0 (0/0/2/0.2.0) --Boot&lt;BR /&gt;Boot: lvol1     on:     /dev/dsk/c1t2d0&lt;BR /&gt;                        /dev/dsk/c2t2d0&lt;BR /&gt;Root: lvol3     on:     /dev/dsk/c1t2d0&lt;BR /&gt;                        /dev/dsk/c2t2d0&lt;BR /&gt;Swap: lvol2     on:     /dev/dsk/c1t2d0&lt;BR /&gt;                        /dev/dsk/c2t2d0&lt;BR /&gt;Dump: lvol2     on:     /dev/dsk/c1t2d0, 0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;in /etc/rc.config.d/savecrash&lt;BR /&gt;&lt;BR /&gt;SAVECRASH=1&lt;BR /&gt;&lt;BR /&gt;SAVECRASH_DIR=/var/adm/crash&lt;BR /&gt;&lt;BR /&gt;and in /etc/rc.config.d/crashconf&lt;BR /&gt;&lt;BR /&gt;CRASHCONF_ENABLED=1&lt;BR /&gt;&lt;BR /&gt;Last line in svr3000 (test) syslog before crash:&lt;BR /&gt;&lt;BR /&gt;Dec  6 13:10:56 svr3000 CM-packtest[9869]: cmmodnet -a -i 192.44.162.196 192.44.160.0&lt;BR /&gt;&lt;BR /&gt;Last line of package log file - shows it calling another script to startup Oracle...&lt;BR /&gt;&lt;BR /&gt;In all my years of ServiceGuard I have never seen something like this before...&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/PACKAGE_NAME&gt;</description>
      <pubDate>Tue, 06 Dec 2005 15:39:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944948#M699653</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-12-06T15:39:12Z</dc:date>
    </item>
    <item>
      <title>Re: Node keeps crashing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944949#M699654</link>
      <description>Is your networking on svr3000 OK?  It appears that the heartbeat may be timing out.</description>
      <pubDate>Tue, 06 Dec 2005 17:59:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944949#M699654</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2005-12-06T17:59:38Z</dc:date>
    </item>
    <item>
      <title>Re: Node keeps crashing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944950#M699655</link>
      <description>As far as I know Network ios fine - I did 1000 pings to both the primary and both hb ip's - both ways and 0% packet loss...&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Dec 2005 18:02:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944950#M699655</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-12-06T18:02:40Z</dc:date>
    </item>
    <item>
      <title>Re: Node keeps crashing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944951#M699656</link>
      <description>Hi Geoff,&lt;BR /&gt;&lt;BR /&gt;It seems that the test node had initiating the TOC of it own.&lt;BR /&gt;&lt;BR /&gt;I would just start the node using cmrunnod &lt;TEST-NODE&gt;. This is just to ensure the cluster service of the node work OK under the configured cluster enviornment.&lt;BR /&gt;Then the further debugging could be done at the package level i,e. cluster services , application startup and monitoring.&lt;BR /&gt; &lt;BR /&gt;I am just wondering about the line in syslog about cmmodnet . It maybe a case the command is not going through may be&lt;BR /&gt;hanged or something. I would very the package IP conflict.  Since the node was crashed before , it may be required&lt;BR /&gt;to clean up the pakcage IP using cmmodnet -r before starting the package.&lt;BR /&gt;&lt;BR /&gt;Did you check the /etc/shutdownlog on this node? &lt;BR /&gt;&lt;BR /&gt;You can check the SGFR as well using cmfmtfr &lt;BR /&gt;&lt;BR /&gt;&lt;/TEST-NODE&gt;</description>
      <pubDate>Tue, 06 Dec 2005 19:33:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944951#M699656</guid>
      <dc:creator>Sameer_Nirmal</dc:creator>
      <dc:date>2005-12-06T19:33:36Z</dc:date>
    </item>
    <item>
      <title>Re: Node keeps crashing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944952#M699657</link>
      <description>Well - turns out I have a bad I/O board HPMC in /var/tombstones.&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Dec 2005 19:46:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944952#M699657</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-12-06T19:46:58Z</dc:date>
    </item>
    <item>
      <title>Re: Node keeps crashing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944953#M699658</link>
      <description>Case seems solved - up over 30 minutes and no crash....&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Tue, 06 Dec 2005 23:59:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/node-keeps-crashing/m-p/4944953#M699658</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-12-06T23:59:35Z</dc:date>
    </item>
  </channel>
</rss>

