Managing HP Serviceguard A.11.20.20 for Linux, March 2014

c. Apply the package configuration once the verification is successful:
#cmapplyconf -P <pkg_name>
d. Configure the application to use the mount point that is added.
• If you are deleting a module or parameter from the module, you must remove the configuration
from the application and later delete from the Serviceguard.
For example, to delete a mount point:
a. Remove the mount point from the application.
b. Edit the package configuration file and remove the mount point.
c. Verify the package configuration file:
#cmcheckconf -P <pkg_name>
d. Apply the package configuration once the verification is successful:
#cmapplyconf -P <pkg_name>
For limitations on online reconfiguration of serviceguard-xdc package, see Online Reconfiguration
of serviceguard-xdc Modular Package Parameters.
7.8.9.1 Handling Failures During Online Package Reconfiguration
During online package reconfiguration, if there are any failure the
online_modification_failed flag is set to yes and the following restrictions apply to the
package:
• The global switching of the package is disabled. This means, the package cannot failover to
the adoptive node. For more information, see cmviewcl (5) manpage.
• Live application detach (LAD) of the node where the package reconfiguration has failed are
not allowed.
• The package cannot be put into maintenance mode when an
online_modification_failed flag is set to yes.
• You cannot modify the package configuration online. For more information, see cmapplyconf
(1m) manpage.
The online_modification_failed flag can be cleared in one of the following ways:
• Halting the package using cmhaltpkg command. For more information, see cmhaltpkg
(1m) manpage.
• A new option -f is introduced for cmmodpkg command that can be used to clear the flag.
The -f option must be used after fixing the errors found during the previous online
reconfiguration of the package. This option is applicable for both failover and multi-node
packages.
For example, if you enter a wrong fs_type value while adding a new filesystem to the pkg1.
*****************************
Package log during this time:
*****************************
Nov 28 23:41:19 [e-mail] master_control_script.sh[23516]: ###### reconfiguring package pkg1 ######
Nov 28 23:41:20 [e-mail] pr_util.sh[23621]: New VG vg_dd0
Nov 28 23:41:20 [e-mail] pr_util.sh[23621]: sg_activate_pr: activating PR on /dev/sdc
Nov 28 23:41:21 [e-mail] volume_group.sh[23687]: New VG vg_dd0
Nov 28 23:41:21 [e-mail] volume_group.sh[23687]: Attempting to addtag to vg vg_dd0...
Nov 28 23:41:21 [e-mail] volume_group.sh[23687]: addtag was successful on vg vg_dd0.
Nov 28 23:41:21 [e-mail] volume_group.sh[23687]: Activating volume group vg_dd0 .
Nov 28 23:41:22 [e-mail] filesystem.sh[23808]: FS added or changed /dev/vg_dd0/lvol3
Nov 28 23:41:22 [e-mail] filesystem.sh[23808]: Checking filesystems:
/dev/vg_dd0/lvol3
e2fsck 1.41.12 (17-May-2010)
mount: wrong fs type, bad option, bad superblock on /dev/vg_dd0/lvol3,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
:
:
248 Cluster and Package Maintenance