Top
PRIMECLUSTER Messages
FUJITSU Software

5.2.3 Non-fatal error messages

Advertisement Client : can't open datagram socket. errno = errno

Content:

The network communication socket of the shutdown daemon was not created successfully. When this message is output, an unintended node may be forcibly stopped when the nodes are forcibly stopped.

Corrective action:

Execute the following command.

# /opt/SMAW/bin/sdtool -s

When "The RCSD is not running" is displayed, execute the following commands to start the shutdown facility.

# /opt/SMAW/bin/sdtool -b

Execute the following command and check the result.

# /opt/SMAW/bin/sdtool -s
  • When Init State is InitWorked and Test State is TestWorked

    No action is required.

  • When Init State is InitFailed or Test State is TestFailed

    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."

  • Other than the above status

    Wait for a while and then execute the above command again. Check the result.

Advertisement Client : sendto error on socket errno errno

Content:

The shutdown daemon failed to send data by the network communication. When this message is output, an unintended node may be forcibly stopped when the nodes are forcibly stopped.

Corrective action:

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."

Calculation of sum of machine weights failed

Content:

An internal error occurred in the program.

Corrective action:

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."

checkAdmInterface : can't bind local address. errno=errno
Advertisement server: can't bind local address, errno errno

Content:

A network communication of the shutdown daemon is impossible. When this message is output, an unintended node may be forcibly stopped when the nodes are forcibly stopped.

Corrective action:

Check if the IP address or the host name that is specified in the rcsd.cfg is valid (host name is registered in the /etc/inet/hosts file on Solaris and on Linux, it is registered in the /etc/hosts file) .If the IP address or the host name is invalid, correct them and then execute the following commands to restart the shutdown facility.

# /opt/SMAW/bin/sdtool -e
# /opt/SMAW/bin/sdtool -b

If the conditions are satisfied, 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."

ERROR:Admin LAN and CIP on the same interface

Content:

The same host name or the IP address is specified for both the configuration definition file of CIP and the configuration definition file of the shutdown daemon. When this message is output, an unintended node may be forcibly stopped when the nodes are forcibly stopped.

Corrective action:

Check that the same host name or the IP address is not specified for both the configuration definition file of CIP and the configuration definition file of the shutdown daemon.

If the same host name or the IP address is specified, configure CIP and the shutdown agent correctly. See "PRIMECLUSTER Installation and Administration Guide" for configuration.

If the same host name or the IP address is not specified, execute the following commands to restart the shutdown facility.

# /opt/SMAW/bin/sdtool -e
# /opt/SMAW/bin/sdtool -b

If the conditions are satisfied, 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."

Error in option specification. (option:option)

Content:

The option is not specified properly.

Corrective action:

Specified the option properly and then execute it again.

Failed to convert AdvData to XDR: string

Content:

The transmitted data was not converted properly in the network communication of the shutdown daemon. When this message is output, an unintended node may be forcibly stopped when the nodes are forcibly stopped.

Corrective action:

Execute the following commands.

# /opt/SMAW/bin/sdtool -s

Then "The RCSD is not running" is displayed, execute the following command to start the shutdown facility.

# /opt/SMAW/bin/sdtool -b

Execute the following command and check the result.

# /opt/SMAW/bin/sdtool -s
  • When Init State is InitWorked and Test State is TestWorked

    No action is required.

  • When Init State is InitFailed or Test State is TestFailed

    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."

  • Other than the above status

    Wait for a while and then execute the above command again. Check the result.

Failed to convert XDR to advData: string

Content:

The received data was not converted properly in the network communication of the shutdown daemon. When this message is output, an unintended node may be forcibly stopped when the nodes are forcibly stopped.

Corrective action:

Execute the following commands.

# /opt/SMAW/bin/sdtool -s

Then "The RCSD is not running" is displayed, execute the following command to start the shutdown facility.

# /opt/SMAW/bin/sdtool -b

Execute the following command and check the result.

# /opt/SMAW/bin/sdtool -s
  • When Init State is InitWorked and Test State is TestWorked

    No action is required.

  • When Init State is InitFailed or Test State is TestFailed

    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."

  • Other than the above status

    Wait for a while and then execute the above command again. Check the result.

FATAL ERROR: Rcsd fails to continue. Exit now.

Content:

An error occurred and the shutdown daemon (rcsd) was ended abnormally. When this message is output, an unintended node may be forcibly stopped when the nodes are forcibly stopped.

Corrective action:

Check if error messages of the shutdown facility have been output before this message is output. If the error messages are output, follow them for the corrective action.

When no error messages of the shutdown facility are output, 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."

Host list(hlist) Empty

Content:

An internal error has occurred.

Corrective action:

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."

The shutdown attempt for host <hostname> could not complete - all SA's failed

Content:

All shutdown agents failed to forcibly stop the node <hostname>.

Corrective action:

Check the status of the cluster node and the cluster applications by Cluster Admin.

Depending on the situation, take the following actions manually:

  • Stop the cluster node

  • Recover the LEFTCLUSTER state

  • Clear the Wait state of SysNode

  • Switch the cluster application

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."

Note

This message may be output if error occurs in the ESXi host in an environment that uses VMware vSphere HA. However, if the virtual machine has successfully migrated by VMware vSphere HA and the operation has resumed, no action is required.