<?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: AUTO_START in MC/SG 11.12 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004041#M710276</link>
    <description>Hi,&lt;BR /&gt;I'm sorry to confuse you but I misstankingly wrote that I'm "AUTO_START YES", instead I'm using (the correct parameter) "AUTO_RUN YES" in my config file.&lt;BR /&gt;&lt;BR /&gt;I have attached both my cluster and package files to this message.&lt;BR /&gt;&lt;BR /&gt;The output on both nodes of:&lt;BR /&gt;swlist -l fileset -a state | grep -i serviceguard&lt;BR /&gt;&lt;BR /&gt;# ServiceGuard&lt;BR /&gt;  ServiceGuard.CM-SG                    configured&lt;BR /&gt;&lt;BR /&gt;/BR</description>
    <pubDate>Sun, 22 Jun 2003 16:05:39 GMT</pubDate>
    <dc:creator>Patrik Nilsson_1</dc:creator>
    <dc:date>2003-06-22T16:05:39Z</dc:date>
    <item>
      <title>AUTO_START in MC/SG 11.12</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004037#M710272</link>
      <description>Hi,&lt;BR /&gt;I have a 2 node cluster where I cannot get my packages to auto start when I boot the servers. The cluster is started but my packages are not.&lt;BR /&gt;I have put "AUTO_START YES" in package config but after boot cmviewcl shows "AUTO_RUN disabled"&lt;BR /&gt;&lt;BR /&gt;Here is my package configuration from cmscancl&lt;BR /&gt;#######&lt;BR /&gt;Package information:&lt;BR /&gt;&lt;BR /&gt;   package ID 24579:&lt;BR /&gt;      package name:                     dbprogr&lt;BR /&gt;      package global flags:             5&lt;BR /&gt;                                        (Package Switch Enabled)&lt;BR /&gt;                                        (Package Local Switch Enabled)&lt;BR /&gt;                                        (Configured Node Failover)&lt;BR /&gt;                                        (Manual Failback)&lt;BR /&gt;      package run script:               /etc/cmcluster/dbprogr/dbprogr.sh&lt;BR /&gt;      package run timeout:              300     (seconds)&lt;BR /&gt;      package halt script:              /etc/cmcluster/dbprogr/dbprogr.sh&lt;BR /&gt;      package halt timeout:             300     (seconds)&lt;BR /&gt;      package primary node:             progr&lt;BR /&gt;      package alternate node:           roam&lt;BR /&gt;      package subnet:                   192.168.1.0&lt;BR /&gt;&lt;BR /&gt;      package services:&lt;BR /&gt;        service ID:                     2&lt;BR /&gt;          service name:                 dbprogr_serv&lt;BR /&gt;          service halt timeout:         290     (seconds)&lt;BR /&gt;          service fail fast:            Disabled&lt;BR /&gt;&lt;BR /&gt;   package ID 57602:&lt;BR /&gt;      package name:                     dbroam&lt;BR /&gt;      package global flags:             5&lt;BR /&gt;                                        (Package Switch Enabled)&lt;BR /&gt;                                        (Package Local Switch Enabled)&lt;BR /&gt;                                        (Configured Node Failover)&lt;BR /&gt;                                        (Manual Failback)&lt;BR /&gt;      package run script:               /etc/cmcluster/dbroam/dbroam.sh&lt;BR /&gt;      package run timeout:              300     (seconds)&lt;BR /&gt;      package halt script:              /etc/cmcluster/dbroam/dbroam.sh&lt;BR /&gt;      package halt timeout:             300     (seconds)&lt;BR /&gt;      package primary node:             roam&lt;BR /&gt;      package alternate node:           progr&lt;BR /&gt;      package subnet:                   192.168.1.0&lt;BR /&gt;&lt;BR /&gt;      package services:&lt;BR /&gt;        service ID:                     2&lt;BR /&gt;          service name:                 dbroam_serv&lt;BR /&gt;          service halt timeout:         290     (seconds)&lt;BR /&gt;          service fail fast:            Disabled&lt;BR /&gt;#####&lt;BR /&gt;&lt;BR /&gt;Any ideas? What have I forgot to do?&lt;BR /&gt;/BR</description>
      <pubDate>Sat, 21 Jun 2003 17:22:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004037#M710272</guid>
      <dc:creator>Patrik Nilsson_1</dc:creator>
      <dc:date>2003-06-21T17:22:49Z</dc:date>
    </item>
    <item>
      <title>Re: AUTO_START in MC/SG 11.12</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004038#M710273</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have A.11.14 installed. The corresponding parameter is "AUTO_RUN YES" in the package configuration file. In older versions (A.11.09) this parameter was PKG_SWITCHING_ENABLED.&lt;BR /&gt;&lt;BR /&gt;Attach your package configuration file if you can with dummy entries for the hostnames/subnets etc.,&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Sat, 21 Jun 2003 17:44:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004038#M710273</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2003-06-21T17:44:32Z</dc:date>
    </item>
    <item>
      <title>Re: AUTO_START in MC/SG 11.12</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004039#M710274</link>
      <description>Hmmm, my notes indicate 'PKG_SWITCHING_ENABLED' obsoleted in MC/SG version A.11.12, its indicated here.&lt;BR /&gt;&lt;BR /&gt;From both nodes can you:&lt;BR /&gt;&lt;BR /&gt;swlist -l fileset -a state | grep -i serviceguard&lt;BR /&gt;&lt;BR /&gt;-and-&lt;BR /&gt;&lt;BR /&gt;swlist -l fileset | wc -l&lt;BR /&gt;&lt;BR /&gt;Also, did you verify the package?&lt;BR /&gt;&lt;BR /&gt;cmcheckconf -P configuration.file</description>
      <pubDate>Sat, 21 Jun 2003 20:37:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004039#M710274</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2003-06-21T20:37:06Z</dc:date>
    </item>
    <item>
      <title>Re: AUTO_START in MC/SG 11.12</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004040#M710275</link>
      <description>IMHO, I would never have MC/SG nor it's packages auto start on a reboot.  I don't do that now.&lt;BR /&gt;&lt;BR /&gt;If a server crashed/rebooted on it's own - you should determine "why" prior to starting up any packages...for example, what if the server that has your Production system crashes?  well, Prod would then start up on your fail-over node...then, when your crashed box starts up, Prod is going to try to start - it should fail and will mark the package as non startable on that node...&lt;BR /&gt;&lt;BR /&gt;What if a disk was failing on the Prod box - and when the machine rebooted - it was worse - then you may corrupt your database when the package starts up....&lt;BR /&gt;&lt;BR /&gt;Just something to think about...&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 22 Jun 2003 02:09:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004040#M710275</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2003-06-22T02:09:42Z</dc:date>
    </item>
    <item>
      <title>Re: AUTO_START in MC/SG 11.12</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004041#M710276</link>
      <description>Hi,&lt;BR /&gt;I'm sorry to confuse you but I misstankingly wrote that I'm "AUTO_START YES", instead I'm using (the correct parameter) "AUTO_RUN YES" in my config file.&lt;BR /&gt;&lt;BR /&gt;I have attached both my cluster and package files to this message.&lt;BR /&gt;&lt;BR /&gt;The output on both nodes of:&lt;BR /&gt;swlist -l fileset -a state | grep -i serviceguard&lt;BR /&gt;&lt;BR /&gt;# ServiceGuard&lt;BR /&gt;  ServiceGuard.CM-SG                    configured&lt;BR /&gt;&lt;BR /&gt;/BR</description>
      <pubDate>Sun, 22 Jun 2003 16:05:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004041#M710276</guid>
      <dc:creator>Patrik Nilsson_1</dc:creator>
      <dc:date>2003-06-22T16:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: AUTO_START in MC/SG 11.12</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004042#M710277</link>
      <description>Hi Patrick,&lt;BR /&gt;&lt;BR /&gt;Well in that case, I would suggeset to reapply the package  configuration and observe 'cmviewcl -v -p package_name". &lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Sun, 22 Jun 2003 16:58:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004042#M710277</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2003-06-22T16:58:33Z</dc:date>
    </item>
    <item>
      <title>Re: AUTO_START in MC/SG 11.12</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004043#M710278</link>
      <description>So what do the package logs say?&lt;BR /&gt;if the packages have attempted to start at all, it will be logged there, and probably the reason why it fails to start.&lt;BR /&gt;My guess is it tried to start on one node, fails, tries to start on the other node,, and then fails again.Also, what does cmviewcl show?&lt;BR /&gt;</description>
      <pubDate>Sun, 22 Jun 2003 20:26:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004043#M710278</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2003-06-22T20:26:30Z</dc:date>
    </item>
    <item>
      <title>Re: AUTO_START in MC/SG 11.12</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004044#M710279</link>
      <description>A)  Do you have AUTOSTART_CMCLD=1 in /etc/rc.config.d/cmcluster?&lt;BR /&gt;&lt;BR /&gt;B)  In the cluster.ascii file there is also the parameter 'AUTO_START_TIMEOUT'.  Default 600 seconds.  Compare this number after using this formula.&lt;BR /&gt;&lt;BR /&gt;"...value equal to the boot time of the slowest booting node minus the boot time of the fastest booting node plus 600 seconds..."&lt;BR /&gt;&lt;BR /&gt;Beside checking for package errors in 'cmcheckconf -P' run 'cmscancl' and attach.&lt;BR /&gt;&lt;BR /&gt;Finally, there is node enabling as well as package switching:&lt;BR /&gt;&lt;BR /&gt;cmmodpkg -e package&lt;BR /&gt;cmodepkg -e -n node</description>
      <pubDate>Sun, 22 Jun 2003 20:48:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-start-in-mc-sg-11-12/m-p/3004044#M710279</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2003-06-22T20:48:03Z</dc:date>
    </item>
  </channel>
</rss>

