Table 30 Error Messages and their Resolution (continued)

Log Messages

Cause

Resolution

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.

 

 

 

 

 

 

 

Failed to get remote site name, cluster might

This message is logged

1.

Wait for the cluster to reform (until there

be in transient state.

because the Serviceguard

 

is no node in reforming state).

Exiting

command cmviewcl

2.

Restart the Site Controller Package.

Or

failed due to cluster

If the cmviewcl command failure is due

reformation or transient

Failed to get local site name, cluster might be

error conditions.

to memory, network or CPU transient error

conditions, fix the issue and restart the Site

in transient state.

 

 

Controller package.

Exiting.

 

 

 

 

 

 

 

 

Error: Failed to get Site Controller EMS

This message is logged

1.

Wait for the cluster to reform (until there

resource value from <node_name>

because the cluster is

 

is no node in reforming state).

Unable to find the site safety latch value at

either reforming or

2.

Restart the Site Controller Package.

remote site siteB

because of transient error

3.

Check there are no issues with the EMS

Or

conditions in the EMS

 

framework using the following command

framework.

 

 

on all the nodes:

Error: Failed to set site safety latch value on

 

 

 

 

resls -s -q /dts/mcsc/

<node_name>

 

 

 

 

 

<site_controller_package_name>

 

 

4. If this command fails, fix the issue and

 

 

 

restart the Site Controller Package.

 

 

 

 

Failed to delete Site Controller detach flag file

This message is logged

1.

Check the file permissions for the

/etc/cmcluster/hrdb_sc/DETACH

because the attempts to

 

DETACH file.

remove the file using the

2.

Remove the file before restarting the Site

 

 

rm command failed.

 

Controller Package.

 

 

 

 

Execution of cmviewcl -f line failed

This message is logged

1.

Wait for the cluster to reform (until there

or

because the Serviceguard

 

is no node in reforming state).

command cmviewcl

2.

Restart the Site Controller Package.

Execution of cmviewcl -v -f line failed

failed due to cluster

If the cmviewcl command failure is due

or

reformation or transient

to memory, network or CPU transient error

Execution of cmviewcl -f line –s config failed

error conditions.

conditions, fix the issue and restart the Site

 

or

 

Controller Package.

 

 

 

Execution of cmviewcl -v -f line –s config failed

 

 

 

 

 

 

Error: Not able to find CVM master node to

This message is logged

Fix the issue that resulted in the CVM

import CVM DG(s)

because the CVM

commands failing and restart the Site

or

commands failed.

Controller Package.

 

 

 

Error Failed to start the CVM DG

 

 

 

<cvm_dg_name> Volumes

 

 

 

 

 

 

Validating Metrocluster Configuration

This error occurs when an

Rename the environment file according to

ERROR: Environment file name is improper

environmental file is

the convention specified. For example, if

already present in the

this error occurred for an MC XPCA

ERROR: Failed to validate

directory that is specified

package, then rename the environment file

/etc/cmcluster/scripts/dts/xpca.sh

as the value for the

as SG_PACKAGE_NAME_xpca.env

Site Controller package validation successful

dts/dts/dts_pkg_dir

 

 

 

parameter, and if it is not

 

 

Troubleshooting 411