Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

Table 8 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
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).
Serviceguard command
Exiting
2. Restart the Site Controller package.
cmviewcl failed due
If the cmviewcl command failure is
due to memory, network, or CPU
Or
Failed to get local site name, cluster might be in
transient state.
to cluster reformation or
transient error
conditions.
transient error 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. Use the following command on all
the nodes to check that there are
no issues with the EMS framework:
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
2. Remove the file before restarting
the Site Controller Package.
the rm command
failed.
This message is logged
because the
Execution of cmviewcl -f line failed
or
1. Wait for the cluster to reform (until
there is no node in reforming state).
Serviceguard command
2. Restart the Site Controller package.
Execution of cmviewcl -v -f line failed
cmviewcl failed due
If the cmviewcl command failure is
due to memory, network, or CPU
or
Execution of cmviewcl -f line –s config failed
to cluster reformation or
transient error
conditions.
transient error conditions, fix the issue
and restart the Site Controller
package.
or
Execution of cmviewcl -v -f line –s config failed
Fix the issue that caused, the failure
of CVM commands, and then 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
This error occurs when
an environmental file is
Validating Metrocluster Configuration
ERROR: Environment file name is improper
example, if this error occurred for analready present in the
ERROR: Failed to validate
/etc/cmcluster/scripts/dts/xpca.sh
MC XPCA package, rename the
environment file as
SG_PACKAGE_NAME_xpca.env
directory that is
specified as the value
for the
Troubleshooting Metrocluster SADTA 75