topic Re: Error when running cmcheckconf in Operating System - HP-UX

Error when running cmcheckconf

Dan Moloisane — Thu, 22 Sep 2005 05:43:54 GMT

hi all,

i 'm getting the ff. error msg when running cmcheckconf -P pkgname. I have already increased the number of configure Pkg parameter to 20 and i have only 3 packages configured.

"Error: The number of packages exceeds the maximum configured packages parameter.
cmcheckconf : Unable to verify package."

Re: Error when running cmcheckconf

Torsten. — Thu, 22 Sep 2005 05:48:56 GMT

Hi Dan,

did you apply the changed value first?

Re: Error when running cmcheckconf

melvyn burnard — Thu, 22 Sep 2005 05:55:18 GMT

you say you have changed the max packages to 20, but have you applied this change with the cmapplyconf yet?
To do this you must first halt the cluster.

Re: Error when running cmcheckconf

Luk Vandenbussche — Thu, 22 Sep 2005 06:19:55 GMT

Hi,

Try the following command to see if your modifications are actif

cmgetconf | grep MAX_CONFIGURED_PACKAGES

Re: Error when running cmcheckconf

Geoff Wild — Thu, 22 Sep 2005 07:47:09 GMT

Did you do a cmapplyconf on the cluster ascii file?

Also - what version of MC/SG are you running?

Do a:

what /usr/lbin/cmcld |grep Date

Rgds...Geoff

Re: Error when running cmcheckconf

Stephen Doud — Thu, 22 Sep 2005 08:29:03 GMT

The original version of Serviceguard permits up to 30 packages. Later versions permit even more packages, so 20 packages is not a ceiling for the product.
Later versions of Serviceguard add the MAX_CONFIGURED_PACKAGES parameter to the cluster configuration ASCII file.
We need to know what version of Serviceguard you are working with:
# what /usr/lbin/cmcld | grep Date
This will report both the version and the patch level.

Next, try this:
# cmviewconf | grep max
Example output:
maximum configured packages: 7

This is the value embedded in the cluster binary file (/etc/cmcluster/cmclconfig).
If the value is less than you thought it should be, then you have not updated the binary file.

To locate the cluster configuration file, try this:
# cd /etc/cmcluster
# grep ^MAX *

If more than one file appear, create a current version:
# cmgetconf CLUSTER.CONF

Edit the file, increase MAX_CONFIGURED_PACKAGES to the value you need and save the file.

Then with the cluster down (cmhaltcl -f), perform:
# cmapplyconf -f -C CLUSTER.CONF

To add another package:
# cmapplyconf -f -P /

To start the cluster:
# cmruncl