Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP A.11.00

Table 9 Error Messages and their resolution (continued)
ResolutionCauseLog Messages
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
Unable to execute command.
Dependency on the following packages not
met: crspkg.
1. Verify the log file of the failed package.
2. Identify and fix the problem. It is
possible that the CRS MNP packages
are not running.
Controller Package has
failed to start one or more
packages that it manages.
cmrunpkg: Unable to start some package or
package instances.
3. Enable node switching for the failed
MNP package.
This situation occurs
because the package
Verify the log files of the packages managed
by Site Controller for more details.
4. Clean the site using the cmresetsc
tool.
dependency configured
for the packages that
Verify for any error messages in the package
log file on all nodes in the site siteA for the
5. Restart the Site Controller Package.
failed is not met on this
site.
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 earlier startup
Starting Site Controller(hrdb_sc) on site siteA.
Earlier startup of Site Controller (hrdb_sc) on
the site siteA has failed
1. Verify the log files of all the packages
managed by Site Controller Package on
the site.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.
Verify 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 earlier
Starting Site Controller (hrdb_sc) on site siteB.
Site Controller start up on the site siteA has
failed.
1. Verify 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 the issues and fix them.
Clean up the site siteA and start hrdb_sc again.
on the remote site. In this
3. Enable node switching for the package
managed by Site Controller Package on
the other site.
Fix any issue reported in the package log files
and enable node switching for the packages
on nodes they have failed.
case, the remote site is
siteB.
4. Clean the remote site using the
cmresetsc tool on a node in the other
site.
Reset the site siteA using cmresetsc command
and start hrdb_sc again.
5. Restart the Site Controller Package.
Site Controller startup failed.
88 Troubleshooting