Hitachi

HA Monitor Cluster Software Messages


KAMN415-W

The request of HAMON_UAPNAME:aa....aa is not accepted.

Reason:bb....bb. Process ID:cc....cc.

An invalid request was received by the program name indicated by HAMON_UAPNAME. The request is ignored. Note that the specification for the HAMON_UAPNAME environment variable is a program name.

aa....aa: Program name

bb....bb: Cause code

Cause code

Meaning

1

Invalid program name

The causes are as follows:

Definition error
  • The program name specified in the HAMON_UAPNAME environment variable is not specified in the name operand of the monitor-mode program environment definition.

  • The server specified in the server_alias operand of the monitor-mode program environment definition is not running or is not defined in the server environment definition.

  • nouse is specified in the program operand of the server environment definition of the server specified in the server_alias definition of the monitor-mode program environment definition.

Operation error
  • After the server environment definition or monitor-mode program environment definition were corrected, a UAP was started manually without restarting the server.

  • A UAP was started manually without starting the server specified in the server_alias operand of the monitor-mode program environment definition.

2

Timing for invoking an API is invalid

An API was invoked at an invalid time, generally as a result of a UAP being operated manually.

3

The hamon_patrolstart function was invoked multiple times

cc....cc: Requesting process ID

S:

Terminates processing.

O:

Contact a system administrator.

Action:

Take one of the following actions, as indicated by the cause code:

Cause code

Corrective action

1

For a definition error, carefully review the definition, and then restart the server.

If the server did not restart after the definition was corrected, restart the server.

If a UAP was manually started without starting the server, start the server. To continue without starting the server and without monitoring the UAP with HA Monitor, specify nouse as the HAMON_API_PATROL environment variable, and then start the UAP.

2

Check the server and UAP status, and then start the UAP manually.

3

Check whether the hamon_patrolstart function has been invoked multiple times, and then correct the UAP, if necessary.