cmviewcl –v –f line <MNP Package name>

Check for the field last_halt_failed under each instance of the MNP package. When set to Yes, that instance of the MNP package did not successfully execute the halt script when it was halted. Check for all instances.

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 30 describes the error messages that are displayed and the recommended resolution.

Table 30 Error Messages and their Resolution

Log Messages

Cause

Resolution

 

 

 

 

Starting Site Controller (hrdb_sc) on site siteB.

The critical package at

1.

Clean the nodes on siteA and enable

Site safety latch at site siteA is open.

siteA is still running.

 

node switching for the Site Controller

 

 

Package.

Checking if site failover conditions are met.

 

 

 

2.

Restart the Site Controller Package on

Critical package hrdb at site siteA is up.

 

 

 

siteA.

Error: Site failover conditions are not met.

 

 

 

Unexpected Site Controller startup.

 

 

 

Unable to initiate site failover at site SiteB.

 

 

 

Site Controller startup failed.

 

 

 

 

 

 

 

Starting Site Controller (hrdb_sc) on site siteB.

An MNP package

1.

Check the MNP package log on all the

Site safety latch at site siteA is open.

managed by the Site

 

nodes on which it failed to run the halt

Controller Package at

 

script successfully.

Checking if site failover conditions are met.

 

siteA has not halted

2.

Clean any stray resources that are still

Package hrdb has not halted cleanly on node

clean on at least one of its

 

online on the node.

<node name>.

nodes.

3.

Re-enable node switching for the MNP

Unable to initiate site failover at site siteB.

 

 

package on the node.

Site Controller startup failed.

 

4.

Restart the Site Controller Package.

 

 

 

 

 

 

Starting Site Controller (hrdb_sc) on site siteB.

The Site Controller was

Start the Site Controller Package on the site

Site safety latch at site siteA is open.

halted in the

where it was previously halted in the

DETACHmode at site

DETACH mode.

Checking if site failover conditions are met.

siteA.

 

 

Error: Site failover conditions are not met.

 

 

 

Unexpected Site Controller startup.

 

 

 

Unable to initiate site failover at site siteB.

 

 

 

Site Controller startup failed

 

 

 

 

 

 

 

Unable to execute command.

A package dependency

1.

Check the log file of the failed package.

Dependency on the following packages not

condition is not met on

2.

Identify and fix the problem. It is

met: crspkg.

this site.

 

possible that the CRS MNP packages

cmrunpkg: Unable to start some package or

 

 

are not running.

 

3.

Enable node switching for the failed

package instances.

 

 

 

MNP package.

Check the log files of the packages managed

 

 

 

 

 

by Site Controller for more details.

 

 

 

 

 

 

 

Troubleshooting 407