5.2.1 Information Messages for which Corrective Action is Unnecessary

Advertisement server successfully started

Content:

The network communication of the shutdown daemon has been started correctly.

After the delay of value seconds, nodename would kill:

Content:

The node nodename will forcibly stop other nodes after value seconds.

All cluster hosts have reported their weight

Content:

The node successfully received the data from all cluster nodes when it forcibly stopped these nodes.

All hosts in the shutdown list are DOWN. Delay timer is terminated

Content:

The shutdown process of the nodes is terminated because all the nodes to be forcibly stopped are already shut down.

Already killed node : nodename, ignoring InvokeSA()

Content:

The node nodename is already forcibly stopped. A request for the shutdown agent to stop the node nodename is ignored.

A reconfig request came in during a shutdown cycle, this request was ignored

Content:

The request to reconfigure the shutdown daemon (sdtool -r) is ignored because the node is forcibly stopped.

Corrective action:

No action is required when the shutdown daemon is unnecessary to be reconfigured. When the shutdown daemon should be reconfigured, execute the following commands after the node is forcibly stopped to restart the shutdown facility (SF).

# /opt/SMAW/bin/sdtool -e

# /opt/SMAW/bin/sdtool -b

A reconfig request is being processed. This request was ignored

Content:

The request to reconfigure the shutdown daemon (sdtool -r) is ignored because the shutdown daemon is under configuration.

Corrective action:

No action is required when the shutdown daemon is unnecessary to be reconfigured. When the shutdown daemon should be reconfigured again, wait for a while and then execute the following commands to restart the shutdown facility (SF).

# /opt/SMAW/bin/sdtool -e

# /opt/SMAW/bin/sdtool -b

A request to clean rcsd log files came in during a shutdown cycle, this request was ignored

Content:

Log files of the shutdown daemon is not renewed (reopened) because the node is forcibly stopped.

Corrective action:

No action is required when the log files of the shutdown daemon is unnecessary to be renewed (reopened). When the log files of the shutdown daemon should be renewed (reopened), execute the following commands after the node is forcibly stopped to renew (reopen) the log files of the shutdown daemon.

# /opt/SMAW/bin/sdtool -l

A Shutdown request for host nodename is already in progress. Merging this request with the original request

Content:

The request to forcibly stop the node nodename is ignored because the node is already forcibly stopped.

A shutdown request has come in during a test cycle, test of Shutdown Agent PID pid will be terminated

Content:

This message is output when sdtool -k is called while rcsd is testing the shutdown agent.

Corrective action:

This message does not indicate particular problems. No action is required.

Broadcasting KRlist...

Content:

For the forcible shutdown of the nodes, each node starts to send and receive the data of the forcible shutdown request.

Cleaning advertisements from the pipe name

Content:

All the nodes have been forcibly stopped. Information from all the cluster nodes, which were received when the nodes were forcibly stopped, is discarded.

cleaning pending InvokeSA()

Content:

The pending request for the shutdown agent is executed again.

Cleaning RCSD log files

Content:

Log files of the shutdown agent are started to be renewed (reopened).

CLI request to Shutdown host nodename

Content:

The request to forcibly stop the node nodename is received.

could not get NON machine weights from RMS

Content:

The total weight values of all the configured userApplication were not collected successfully. RMS may not be installed in this node or RMS does not work correctly.

disablesb.cfg does not exist, errno errno

Content:

This is the internal information of the shutdown daemon.

Eliminating host nodename has been taken care of

Content:

The target node to be forcibly stopped is not shut down because the node has been already stopped.

Failed to break into subclusters

Content:

This is the information when the nodes are forcibly stopped.

Failed to calculate subcluster weights

Content:

This is the information when the nodes are forcibly stopped.

Failed to cancel thread, thread of string string of host nodename

Content:

The thread <thread> for the node <nodename> is not cancelled successfully.

Failed to prune the KR list

Content:

This is the information when the nodes are forcibly stopped.

Failed to VerifyMaster

Content:

This is the information when the nodes are forcibly stopped.

Finished Resolving Split.

Content:

The process to forcibly stop the nodes is completed.

Finished wait for Delay Timer.starting to resolve split

Content:

The process to forcibly stop the nodes is started after the wait time has passed.

For string: MyCH = 0xvalue, MySC = 0xvalue

Content:

This is the information when the nodes are forcibly stopped.

Forced to re-open CLI pipe due to a missing pipe name

Content:

A pipe for the command interface of the shutdown daemon is re-created because it has an error.

Corrective action:

When a pipe for the command interface has an error, the shutdown facility re-creates a pipe. No action is required because this does not affect other processes that are operated by the system.

Forced to re-open CLI pipe due to an invalid pipe name

Content:

A pipe for the command interface of the shutdown daemon is re-created because it has an error.

Corrective action:

When a pipe for the command interface has an error, the shutdown facility re-creates a pipe. No action is required because this does not affect other processes that are operated by the system.

Forced to re-open CLI pipe due to failed stat pipe name errno

Content:

A pipe for the command interface of the shutdown daemon is re-created because it has an error.

Corrective action:

When a pipe for the command interface has an error, the shutdown facility re-creates a pipe. No action is required because this does not affect other processes that are operated by the system.

Fork Shutdown Agent(PID pid) to action host nodename

Content:

The shutdown agent <Shutdown Agent> is started to execute the action <action> for the node <nodename>.

Gathering CF Status

Content:

The initial process for CF of the shutdown daemon is started.

getservbyname returned portnumber as the port for sfadv server

Content:

A network communication port number portnumber for the shutdown daemon is successfully obtained.

host nodename has already been killed. Ignoring this request

Content:

The request to forcibly shut down the node nodename is ignored because the node has been already stopped.

Host nodename has been put in the shutdown list

Content:

The node <nodename> is already in the shutdown node list.

host nodename is the value highest weight in the cluster

Content:

This is the information of the survival priority.

Host nodename, MA Monitoring Agent, MAHostGetState():string

Content:

MAHostGetState() works correctly in the MA monitor thread.

Host nodename, MA Shutdown Agent, MAHostInitState() returned value

Content:

MAHostInitState() is executed in the MA monitor thread.

Host nodename (reported-weight:value) wants to kill nodename - master nodename

Content:

This is the information of the forcible shutdown request for each node.

icf_ping returned value(string)

Content:

The node status is checked through cluster interconnects.

In string : Select returned value, errno errno

Content:

The select function of the shutdown daemon returns abnormally.

Corrective action:

The shutdown facility re-creates a pipe for the target network communication to restart the process. No action is required because this does not affect other processes that are operated by the system.

InvokeSA( nodename, action, number )

Content:

The action action for the node nodename is pending.

Kill requests:

Content:

The forcible shutdown request information for each node is output.

Kill Requests are:

Content:

The forcible shutdown request information for each node is output.

KR from nodename to kill nodename had master nodename, now has master nodename

Content:

This is the information when the node is forcibly stopped.

MA Monitoring Agent reported host nodename leftcluster, state string

Content:

The node status change is detected.

No kill requests from my subcluster

Content:

The forcible shutdown request is not sent for the node cluster that includes the local node.

node-factor set to default value: value

Content:

This is the information to calculate the survival priority.

node-factor updated to : value

Content:

This is the information to calculate the survival priority.

nodename was leaving cluster

Content:

The node nodename is being separated from the cluster.

pclose failed for command.errno = errno

Content:

An error occurred when the command command is terminated. This does not cause any problems.

Pending InvokeSA():

Content:

The request to the pending shutdown agent is output.

PID pid has indicated a {successful | failed} host action

Content:

When the shutdown agent is terminated, it returned the normal value or abnormal value.

PID pid has indicated a successful host shutdown

Content:

PID pid stopped the nodes successfully.

Processing event for host nodename

Content:

The process of CF event <event> of the received node <nodename> has started.

RCSD already running

Content:

Shutdown daemon is already started.

Corrective action:

Shutdown daemon is unnecessary to be restarted
No action is required.
Shutdown daemon is necessary to be restarted
Execute the following commands to restart the shutdown facility (SF).
```
# /opt/SMAW/bin/sdtool -e
```
```
# /opt/SMAW/bin/sdtool -b
```

When this corrective action does not work, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."

RCSD controlled daemon exit completed

Content:

The shutdown daemon is successfully terminated.

RCSD has detected some data on the pipe RCSDNetPipe.

Content:

The shutdown daemon has detected the transmitted data from other nodes.

RCSD log files cleaned successfully

Content:

Log files of the shutdown daemon are successfully renewed (reopened).

RCSD started

Content:

Shutdown daemon is started.

Received the string command from the CLI PID pid

Content:

Shutdown daemon received the command request.

Restarting advertisement server thread after a reconfig

Content:

A communication network thread for the shutdown daemon is created.

RMS is NOT running on this system

Content:

RMS may not be installed in this node or RMS does not work correctly.

RMS is running on this system

Content:

RMS works in this node.

SA Shutdown Agent to init host nodename succeeded

Content:

The shutdown agent <Shutdown Agent> for the node <nodename> is successfully initialized.

SA Shutdown Agent to shutdown host nodename succeeded

Content:

The shutdown agent <Shutdown Agent> has successfully shut down the node<nodename>.

SA Shutdown Agent to unInit host nodename succeeded

Content:

The shutdown process of the shutdown agent <Shutdown Agent> for the node <nodename> is successfully completed.

Sending a Dummy KRlist - No Kill req only weight

Content:

When the nodes are forcibly stopped, the forcible shutdown request from the local node to the specified node was not sent. Only the information of the local node was sent to other nodes.

SF will be the Split Brain Manager on this system

Content:

The shutdown facility controls the forcible shutdown of the nodes on this system.

Shutdown request had come in. Reconfig is ignored
Exit request had come in. Reconfig is ignored

Content:

The request to reconfigure the shutdown daemon (sdtool -r) is ignored because the node is already forcibly stopped or the shutdown daemon is under shutdown process.

Corrective action:

No action is required when the shutdown daemon is unnecessary to be reconfigured. When the shutdown daemon should be reconfigured again, wait until the forcible shutdown process of the nodes is completed. When the shutdown daemon is under shutdown process, wait for a while and then execute the following commands to restart the shutdown facility (SF).

# /opt/SMAW/bin/sdtool -e

# /opt/SMAW/bin/sdtool -b

Skipping weight of nodename, it is DOWN

Content:

The node nodename is excluded from the calculation of survival priority because the node is shut down.

Skipping weight of nodename, it has never joined the cluster

Content:

The node nodename is excluded from the calculation of survival priority because the node is not joined the cluster.

sleep n seconds before invoking Shutdown Agent to kill nodename

Content:

The node nodename will be forcibly stopped by the shutdown agent Shutdown Agent after n seconds.

SMAWRrms is installed on this system

Content:

SMAWRrms is installed in this node.

SMAWRrms is NOT installed on this system

Content:

RMS may not be installed in this node.

Split Brain processing completed. Nothing to do on local node

Content:

The survival priority has been calculated.

Split Brain processing is in progress, saving InvokeSA into the Buffer

Content:

The request for the shutdown agent is pending because the node is in the forcible shutdown process.

Starting the Advertisement server on host( IP address ), port:number

Content:

Initialization is started for the network communication of the shutdown daemon.

Starting the RCSD Daemon

Content:

The shutdown daemon is started.

Sub-cluster master nodename, Sub-cluster weight value (value%) count value

Content:

This is the statistical information of the node cluster.

Sub-cluster statistics:

Content:

The statistical information of the node cluster is output.

The RCSD on host nodename is running in CF mode

Content:

The node nodename has been confirmed to have the installed CF.

The SF-CF has received event

Content:

A CF event monitor thread received the CF event <event>.

The SF-CF has successfully declared host nodename event

Content:

The CF event <event> for the node <nodename> is successfully published.

Throwing away the KRlist

Content:

The forcible shutdown request of the nodes is ignored because the target nodes are already unnecessary.

Total Cluster weight is :value

Content:

Total weight of the nodes and the userApplication in the whole cluster is value.

Total Cluster Weight: value, Percentage of Cluster weight missing: value%

Content:

This is the information of the total cluster weight.

Total potential weight is value (value application + value machine)

Content:

This is the information of the total weight of the nodes and the userApplication in the whole cluster.

Total user application weight for all user applications online on local host is value

Content:

This is the total value of all the userApplication that are currently in Online state on the local node.

Total user application weight for the total cluster is value

Content:

This is the total value of all the configured userApplication.

unable to verify admIP: IP address

Content:

This data cannot be used because it was transmitted from the unverified cluster nodes.

Unknown command from sdtool, command value

Content:

Invalid sdtool command line is used.

Corrective action:

Choose the correct parameter to call sdtool.

Waiting for localCHost->CH_delay: n

Content:

The nodes will be forcibly stopped after n seconds.

weight-factor set to default value: value

Content:

This is the information to calculate the survival priority.

weight-factor updated to : value

Content:

This is the information to calculate the survival priority.