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

The unclean nodes might have stray resources. See the MNP package log file on the corresponding
node to identify the reason for the halt script run failure. Clean any stray resources that are still
online in the node and enable node switching on the node for the package. This clears the flag
and allows the Site Controller Package to start. Complete this procedure for all nodes where the
MNP package instance has halted unclean.
# cmmodpkg –e -n <node name> <MNP Package name>
Understanding Site Controller package logs
This section describes the various messages that are logged in the log files and the methods to
resolve those error messages.
Table 8 describes the error messages that are displayed and the recommended resolution.
Table 8 Error messages and their resolution
ResolutionCauseLog Messages
The critical package at
siteA is still running.
Starting Site Controller (hrdb_sc) on site siteB.
Site safety latch at site siteA is open.
1. Clean the nodes on siteA and
enable node switching for the Site
Controller package.
Checking if site failover conditions are met.
2. Restart the Site Controller package
on siteA.
Critical package hrdb at site siteA is up.
Error: Site failover conditions are not met.
Unexpected Site Controller startup.
Unable to initiate site failover at site SiteB.
Site Controller startup failed.
An MNP package
managed by the Site
Starting Site Controller (hrdb_sc) on site siteB.
Site safety latch at site siteA is open.
1. Check the MNP package log on
all the nodes on which it failed to
run the halt script successfully.Controller package at
siteA has not halted
Checking if site failover conditions are met.
2. Clean any stray resources that are
still online on the node.
clean on at least one of
its nodes.
Package hrdb has not halted cleanly on node <node
name>.
3. Enable node switching for the MNP
package on the node.
Unable to initiate site failover at site siteB.
4. Restart the Site Controller package.
Site Controller startup failed.
Start the Site Controller package on
the site where it was previously halted
in the DETACH mode.
The Site Controller was
halted in the DETACH
mode at site siteA.
Starting Site Controller (hrdb_sc) on site siteB.
Site safety latch at site siteA is open.
Checking if site failover conditions are met.
Error: Site failover conditions are not met.
Unexpected Site Controller startup.
Unable to initiate site failover at site siteB.
Site Controller startup failed
A package dependency
condition is not met on
this site.
Unable to run command.
Dependency on the following packages not met:
crspkg.
1. Check the log file of the failed
package.
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.
3. Enable node switching for the
failed MNP package.
Check the log files of the packages managed by Site
Controller for more details.
4. Clean the site using the
cmresetsc tool.
See the Metrocluster documentation for cleanup
procedures needed before restarting the Site
Controller.
5. Restart the Site Controller package.
Site Controller startup failed.
Troubleshooting Metrocluster SADTA 71