Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

Table 30 Error Messages and their Resolution (continued)
ResolutionCauseLog Messages
Check for any error messages in the package
log file on all nodes in the site siteA for the
packages managed by Site Controller
(hrdb_sc).
Fix any issue reported in the package log files
and enable node switching for the packages
on nodes they have failed.
Reset the site siteA using cmresetsc command
and start hrdb_sc again.
Site Controller startup failed.
This message is logged
because the Serviceguard
Failed to get remote site name, cluster might
be in transient state.
1. Wait for the cluster to reform (until there
is no node in reforming state).
command cmviewcl
Exiting
2. Restart the Site Controller Package.
failed due to cluster
If the cmviewcl command failure is due
to memory, network or CPU transient error
Or
Failed to get local site name, cluster might be
in transient state.
reformation or transient
error conditions.
conditions, fix the issue and restart the Site
Controller package.
Exiting.
This message is logged
because the cluster is
Error: Failed to get Site Controller EMS
resource value from <node_name>
1. Wait for the cluster to reform (until there
is no node in reforming state).
either reforming or
Unable to find the site safety latch value at
remote site siteB
2. Restart the Site Controller Package.
because of transient error
conditions in the EMS
framework.
3. Check there are no issues with the EMS
framework using the following command
on all the nodes:
resls -s -q /dts/mcsc/
<site_controller_package_name>
Or
Error: Failed to set site safety latch value on
<node_name>
4. If this command fails, fix the issue and
restart the Site Controller Package.
This message is logged
because the attempts to
Failed to delete Site Controller detach flag file
/etc/cmcluster/hrdb_sc/DETACH
1. Check the file permissions for the
DETACH file.
remove the file using the
rm command failed.
2. Remove the file before restarting the Site
Controller Package.
This message is logged
because the Serviceguard
Execution of cmviewcl -f line failed
or
1. Wait for the cluster to reform (until there
is no node in reforming state).
command cmviewcl
2. Restart the Site Controller Package.
Execution of cmviewcl -v -f line failed
failed due to cluster
If the cmviewcl command failure is due
to memory, network or CPU transient error
or
Execution of cmviewcl -f line –s config failed
reformation or transient
error conditions.
conditions, fix the issue and restart the Site
Controller Package.
or
Execution of cmviewcl -v -f line –s config failed
Fix the issue that resulted in the CVM
commands failing and restart the Site
Controller Package.
This message is logged
because the CVM
commands failed.
Error: Not able to find CVM master node to
import CVM DG(s)
or
Error Failed to start the CVM DG
<cvm_dg_name> Volumes
Rename the environment file according to
the convention specified. For example, if
This error occurs when an
environmental file is
Validating Metrocluster Configuration
ERROR: Environment file name is improper
this error occurred for an MC XPCAalready present in the
ERROR: Failed to validate
/etc/cmcluster/scripts/dts/xpca.sh
package, then rename the environment file
as SG_PACKAGE_NAME_xpca.env
directory that is specified
as the value for the
dts/dts/dts_pkg_dir
Site Controller package validation successful
parameter, and if it is not
Troubleshooting 411