Content:
The rcsd daemon tries to stop the machine now.
The current request cannot be accepted.
Corrective action:
Retry after the machine is completely stopped.
Content:
The rcsd binary may not exist.
Corrective action:
Install the shutdown facility again.
Content:
The product may not been installed properly.
Corrective action:
Reinstall the shutdown facility.
Content:
Log files could not be opened.
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."
Content:
The pipe for rcsd could not be created.
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."
Content:
The communication pipe from sdtool to rcsd could not be opened.
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."
Content:
The rcsd daemon is about to be shut down.
Commands are not allowed.
Corrective action:
Execute commands after the rcsd daemon is started.
Content:
The rcsd failed to execute the command from sdtool.
Corrective action:
Depending on the state when this message was output, take either of the following actions.
If the sdtool -k command is executed in the environment where the ICMP shutdown agent is used
The ICMP shutdown agent does not forcibly stop another node.
Take any one of the following procedures to stop the node manually and forcibly:
[For Solaris]
When stopping the physical environment or the control domain forcibly
Refer to the instruction manual of the main unit.
When stopping the guest domain forcibly
Use a command such as the ldm panic-domain command on the control domain.
# ldm panic-domain <guest domain name to be forcibly stopped>
When stopping the Kernel Zone forcibly
Use a command such as the zoneadm halt command on the global zone.
# zoneadm -z <Kernel Zone name to be forcibly stopped> halt
[For Linux]
In VMware environment
Stop the virtual machine from ESXi host or VMware vCenter Server.
Other than the above
Check if related messages are additionally output.
If additional messages are output, follow them for the corrective action.
If no additional messages were 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."
Content:
The sdtool failed to read the data from the rcsd daemon.
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."
Content:
The sdtool could not receive information from the rcsd.
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."
Content:
The command was not executed successfully because the rcsd daemon was not executed.
Corrective action:
Start the rcsd daemon (sdtool -b) and then execute the command again. Check by the ps command if the rcsd command is started.
Content:
Old pipe files could not be removed.
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."
Content:
The invalid parameter/command line is used.
Corrective action:
Use valid parameters.
Content:
The sdtool could not pass the command to the rcsd.
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."