Prevent package start at cluster start

[Sebastien Masson]

Hi all,

I have a huge cluster of 8 nodes with 30 packages and I want to know how can I prevent the start of all my 30 package when I start the cluster with the cmruncl command... And I want to keep the ability to the package to switch to the fail node when a failure occur.

Thanks

[Roger Baptiste]

hi,

cmruncl without any options will attempt to start the cluster on all the nodes, due to which it will try bringing up the packages of all nodes, as it is configured in the system.
If you do not want this, then run
cmruncl -n
This will start the cluster on only one node (nodename) and start only the packages which are used by that node, instead of all the 30 packages.
Once you are sure of starting the packages, you can run
cmrunnode -n on each of the remaining nodes , this will start the cluster on those nodes and their corresponding packages.

HTH
raj

[Martin Johnson · Accepted solution]

Modify your package scripts to look for a maintenance file. If found do not start the package. Do a "touch /tmp/pkgname_maint" prior to the cmruncl command.

[Helen French]

Hi Sebastian:

This document will be helpful (TKB #UXSGKBRC00004102):

http://us-support2.external.hp.com/cki/bin/doc.pl/sid=83951a35158e143bce/screen=ckiDisplayDocument?docId=200000058849803

HTH,
Shiju

[Sanjay_6]

Hi Sebastien,

Have you tried setting the AUTO_RUN Value to NO in the package configuration file and see if the package still starts at cluster startup. Setting the value of this variable to NO will allow you to start the cluster without starting the packages.

The thing you should now worry about is the failover. So you can try that by doing this, start this package manually once the cluster has started. then shutdown the primary node on which package runs without shutting down the cluster on that node. This will allow you to check the failover.

Do remember, if you make any changes to the package conf file you have to apply those changes to create new cluster binaries.

Hope this helps.

Regds

[Jim Carter]

If you want your packages NOT to start automatically, then you must set AUTO_RUN to NO but you must still define alternate nodes. Once you start a package manually, you can do a cmmodpkg and enable node failover for that package.

I have done this in cases where I want to ensure one package is started and stable before another attempts to start, and it seems to work just fine.

[Jim Carter]

Sorry, I should've said I issue the cmmodpkg as one of the last steps in the start script of the parent package. In other words, if I want pkg_b to start after pkg_a, then I set pkg_b AUTO_RUN to NO, define alternate nodes for it, and as a last startup step for pkg_a, I cmmodpkg pkg_b to autostart on failover.

[Christian Schulze]

from which version of Service Guard on is
AUTO_RUN available in the conf-Files ?

my Version is A.11.09, and by default there is no AUTO_RUN variable in the conf-scripts.

Christian