Top
PRIMECLUSTER Messages
FUJITSU Software

7.18.1 Error messages

<command> command failed. return_value=<value>.

Content:

The command <command> abnormally ended with the return value <value>.

Corrective action:

Check whether the execution environment of <command> is correct.
If sudo is included in the <command>, see "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)" and check whether the configuration of sudo command is executed for the general privileged user of the shutdown facility.
If there are no errors in the execution environment, 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."

Could not find <file>.

Content:

The file <file> does not exist.

Corrective action:

  • /etc/opt/SMAW/SMAWsf/rcsd.cfg
    Configure the shutdown facility.

  • Other files
    Create <file>.

<file> is invalid.

Content:

The content that is described in the file <file> has an error.

Corrective action:

Check the content of the file <file> and add the proper information.

First SSH connection to the guest domain has not been done yet. (node:nodename ipaddress:ipaddress detail:code)

Corrective action:

Complete the user inquiry (such as RSA Key Generation) of the SSH connection first time by using the login user account for the Shutdown Facility to connect SSH to the guest domain from the control domain.
If 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."

No system administrator authority.

Content:

You do not have a system administrator authority.

Corrective action:

Execute the operation as a system administrator.

Saving the configuration information of the logical domain failed.

Corrective action:

Save the configuration information of the logical domains manually in the control domains of the migration source and destination for the target guest domain.

The domain type is not a control domain.

Corrective action:

Check the environment where this command has been executed. Then execute it again in the control domain.

The guest domain information of the specified node name is not registered. (nodename:nodename)

Corrective action:

Execute the clovmmigratesetup -l command to check the registered guest domain information.

The Migration function cannot be used in this environment. (nodename:nodename)

Corrective action:

Check the following points:

  • Is the specified guest domain name correct?

  • Has PRIMECLUSTER been installed in the specified guest domain?

  • Has T007881SP-02 or later (Solaris10) or T007882SP-02 or later (Solaris11) been applied to the specified guest domain?

If the error cause was any one of the above check items, execute this command again.

If the problem is not resolved by the above action, record this message and collect information for an investigation. Then, contact field engineers. For how to collect the investigation information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."

The SA <Shutdown Agent> is not registered.

Content:

The shutdown agent <Shutdown Agent> is not registered.

Corrective action:

Register the shutdown agent <Shutdown Agent>.

The specified guest domain cannot be connected. (nodename:nodename)

Content:

The specified guest domain nodename cannot be connected.

Corrective action:

Check if the information of the guest domain that is specified with clovmmigratesetup command is correct.

- Cluster name of guest domain, CF node name

- IP address

- User name, password

Also connect to the guest domain from the control domain via SSH by using the login user account for the shutdown facility, and complete the user inquiry of the SSH connection first time (such as RSA Key Generation).

If any of the status above is the cause of the connection failure after executing the corrective action, execute this command again.

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