I need to change a package setting

[Terrence]

This is a simple question I think, but I want to confirm that I'm going to do this correctly due to the criticality of the application. This is for a two node cluster of service guard 11.16 running on HPUX 11.23

The RUN_SCRIPT_TIMEOUT & HALT_SCRIPT_TIMEOUT settings in my package config file need to be increased.

I made the change and cmcheckconf runs clean for both the cluster and the package.

During my upcoming maintenance window I am going to run the following commands.

cmhaltcl

vgchange -a n vg01 vg02

cmcheckconf -P pckg.conf

cmapplyconf -P pckg.conf

cmruncl -v

I know this is fairly routine, but I do this so infrequently I thought I'd CMA and ask some people with expertise if I've got it correct.

[Rita C Workman · Accepted solution]

Terrence,

To change the Script timeouts on a package you do not need to stop anything. It can be done with the package & cluster running.

You would need to halt to change network info; or to change the Service timeout or falfast I believe for the version your on.

Regards,
Rita

[Turgay Cavdar]

Look at the doc:
http://docs.hp.com/en/B3936-90079/ch07s05.html?btnNext=next%A0%BB

It says "Script timeouts: Package may be either running or halted." so you dont need to stop your package or cluster. You need to:

1-)Edit the ASCII package configuration file.

2-)Verify your changes
cmcheckconf -v -P pkg1.ascii

3-)Distribute your changes to all nodes:
cmapplyconf -v -P pkg1.ascii

[Terrence]

Thanks for the confirmation. Unfortunately I will need to bounce the cluster anyway. When this originally failed due to the Timeout setting, SG didn't successfully start the package although it did mount the filesystems.

So I started the application manually. SG thinks the package is down.

Also I need to confirm that the timeout setting is long enough now, so I will still have a downtime.

Thanks

[Rita C Workman]

Have you considered setting the Script timouts to...NO_TIMEOUT. It is an option and it might save you from these issues.
======================
"...When this originally failed due to the Timeout setting, SG didn't successfully start the package although it did mount the filesystems.
So I started the application manually. SG thinks the package is down.
Also I need to confirm that the timeout setting is long enough now, so I will still have a downtime...."

>>> SG thinks the pkg is down, but your f/s mounted. I'm thinking SG is running pkg. So run cmviewcl and check this. Cause the script startup kicks off the pgk.cntl file, which mounts the filesystems, and in most kicks off the appl. So I'm thinking the pkg is up and is running even though your appl didn't start.

No matter, you can still just change your timeout settings, with things up and running. You don't need to vgchange anything. Just make your chgs, run pkg cmcheckconf and then cmapplyconf.

Regards,
Rita