Troubleshooting VMs as Serviceguard Packages |
 |
If the distributed guest does not start or failover,
check both the /var/adm/syslog/syslog.log file
and the package log file (/etc/cmcluster/guest—name/guest—name.log).
If a package fails to start, Serviceguard performs
a package halt. The log files include a Halting package section after
the Starting package section that contains the actual starting failure
messages. When you view package log files after a package start failure,
look at the Halting package section as well as the Starting package
section.
If the distributed guest does not fail over, take
the package down using the cmhaltpkg command. Make
sure the guest has the resources it needs to run on the adoptive node
by manually starting the package on the adoptive node with the same
workload using the cmrunpkg command.
If the package does not start under manual control,
stop the cluster and test the guest named compass1.
Use the hpvmmodify command to set
the guest to not be distributed. For example:
# hpvmmodify -P compass1 -i NONE
# hpvmmodify -P compass1 -j 0 |
Use the hpvmstart command to start
the guest with the same VM Host system and workload. Use the virtual
console (hpvmconsole) to make sure the the guest
OS is installed and that applications are running properly.
After testing the guest, create the Serviceguard
package again.
If the guest does not start and displays errors
about storage problems, and you are using logical volumes, the storage
units might not be available to the VM Host. To make the storage units
available , enter the appropriate commands, as follows:
For LVM logical volumes, enter the following commands:
# vgchange -c n /dev/vgxx
# vgchange -a y /dev/vgxx |
For VxVM logical volumes, enter the following commands:
# vxdg import diskgroup-name
# vxvol -g diskgroup-name startall |
If you are using files on a logical volume, also enter
the following command:
# mount /dev/vgxx /mount-point |
After making sure the backing storage devices
are available, restore them to their original state.
Some problems that arise from improper storage
configuration include:
Whole disks — Verify that the VM Host has access
to the disks. If not, the problem might be a hardware or storage subsystem
issue.
LVM - Before starting a package, Serviceguard requires
that all volume groups associated with the package are inactive. For
details about deactivating LVMs, see the Managing Serviceguard manual.
VxVm — Before starting a package, Serviceguard
requires that all disk groups associated with the package are deported.
For details, see the Managing Serviceguard manual.
Files — Before starting a package, Serviceguard
requires that file systems of file backing stores associated with
the package are unmounted.
If the guest has problems accessing network, make
sure the network devices are available on the VM Host system. Packages
do not start if any of their defined subnets are unavailable. This
causes multiple failures if no standby LANs are available, or when
one or more switches, hubs, interfaces or cables fail.
A common issue when starting a package is the
lack of available memory. For more information about providing the
required memory resources, see Chapter 3 .
Creating Distributed Guests |
|
This section describes how to use the hpvmsg_package script to help you configure guests as Serviceguard
packages. If you create the Serviceguard package configuration and
control scripts manually instead, use the following options to the hpvmcreate , hpvmmodify, or hpvmclone command to identify the Serviceguard package
name and to mark the guest as a distributed guest:
Use the -i option to specify the
Serviceguard package. (For example, -i SG_package_name.)
Use the -j 1 option
to specify that the guest is a distributed guest.
For more information, see the hpvmsg_package file.
Printable version
