Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

Table 6 Error Messages and their Resolution (continued)
ResolutionCauseLog Messages
Warning: Site Controller
<site_controller_package_name> not able to set
If the cmviewcl command fails because
of a memory, network or CPU transient
error condition, fix the issue.
reforming or because of
transient error conditions.
the Site Safety Latch value to <value> on node
<node_name>.
Check the Site Controller package
<site_controller_package_name> log for more
details.
Remove the comments specified after the
values of the critical_package
parameter.
This message appears
because a comment is
specified after the
critical_package
When you execute the cmapplyconf -f -P
hrdb_sc.config command, the following
message is displayed:
Failed to validate
/etc/cmcluster/scripts/mscripts/master_control_script.sh.
parameter value in Site
Controller package
configuration file.
On node <node_name> validation failed with:
/etc/cmcluster/scripts/dts/sc.sh[49]:
SC_CRITICAL_PACKAGE: The specified
subscript cannot be greater than 1024.
ERROR: Failed to validate
/etc/cmcluster/scripts/dts/sc.sh
This message is logged
because the Site Controller
Unable to execute command.
Dependency on the following packages not met:
crspkg.
1. Check the log file of the failed
package.
package has failed to start
one or more packages that
2. Identify and fix the problem. It is
possible that the CRS MNP packages
are not running.
cmrunpkg: Unable to start some package or
package instances.
it manages. This situation
occurs because the
3. Enable node switching for the failed
MNP package.
Check the log files of the packages managed
by Site Controller for more details.
package dependency
configured for the
packages that failed is not
met on this site.
4. Clean the site using the cmresetsc
tool.
Check for any error messages in the package
log file on all nodes in the site siteA for the
5. Restart the Site Controller package.
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 previous
Starting Site Controller(hrdb_sc) on site siteA.
Previous startup of Site Controller (hrdb_sc) on
the site siteA has failed
1. Check the log files of all the packages
managed by Site Controller package
on the site.startup of the Site
Controller package failed
on the local site siteA.
2. Identify the issues and fix them.
Clean up the site siteA and start hrdb_sc again
3. Enable node switching for the
package managed by the Site
Controller package on the site.
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).
4. Clean the site using the cmresetsc
tool.
Fix any issue reported in the package log files
and enable node switching for the packages on
nodes they have failed.
5. Restart the Site Controller package.
Reset the site siteA using cmresetsc command
and start hrdb_sc again.
Site Controller startup failed.
This message is logged
because the previous
Starting Site Controller (hrdb_sc) on site siteB.
Site Controller start up on the site siteA has
failed.
1. Check the log files of all the packages
managed by Site Controller package
on the remote site.start-up of the Site
Controller package failed
2. Identify and issues and fix them.
Clean up the site siteA and start hrdb_sc again.
on the remote site. In this
Troubleshooting Metrocluster SADTA 65