Explanation
Execution was attempted with other than super-user permission.
Response
Retry execution with super-user permission.
Explanation
File open processing for command lock failed.
Response
Apply countermeasures as described in errmsg.
Explanation
Execution of this command failed as another sfcfrmstart(8) or sfcfrmstop(8) command was being executed.
Response
Once execution of the other command has terminated, re-execute this command.
Explanation
Connection with the cluster control facility failed.
Response
Confirm that the cluster control facility has already been started.
Explanation
The management partition may be being used on either the self-node or another node.
Response
Wait for the operation of the management partition to end, and then retry.
Explanation
Memory acquisition failed.
Response
Either wait for another process to end, or increase the size of the swap area.
Explanation
Setting file sfcfsrm.conf could not be read.
Response
Perform management according to errmsg.
Explanation
Reading of the management partition failed.
Response
If a disk of the management partition fails, restore the management partition by referring to "9.6 Backup of the management partition information" and "9.7 Restoring of the management partition information."
If a disk failure does not occur, field engineers.
Explanation
The self-node does not belong to a host group.
Response
Using the sfcsetup(8) command, add the self-node to a host group.
Explanation
Start processing for sfcfrmd failed.
Response
After confirming the state of the self-node and that sfcprmd is available, contact field engineers.
Explanation
The sfcfrmd has already been started.
Response
None.
Explanation
As no setting is made to the management partition, the management partition cannot be accessed.
Response
Use the sfcsetup(8) command to set up the management partition. For details, see "9.2 Creating of the management partition."
Explanation
The communication path to sfcprmd cannot be established.
Response
After confirming the state of the self-node and that sfcprmd is available, contact field engineers.
Explanation
State confirmation processing for sfcprmd using several different daemons failed.
Response
After confirming the state of self-node and that sfcprmd is available, contact field engineers.
Explanation
Write processing for the management partition failed.
Response
After confirming that no disk error occurred, contact field engineers.
Explanation
File open processing for editing the sfcfsrm.vers file failed.
Response
Apply countermeasures as described in errmsg.
Explanation
File write processing for editing the sfcfsrm.vers file failed.
Response
Apply countermeasures as described in errmsg.
Explanation
File rename processing for editing the sfcfsrm.vers file failed.
Response
Apply countermeasures as described in errmsg.
Explanation
File access to cancel the suspension of the sfcfrmd daemon's startup failed.
Response
Check if the sfcfrmd daemon is running by ps(1) command.
An example is shown below.
# /bin/ps -e | /bin/grep sfcfrmd <Enter> 27198 ? 00:00:00 sfcfrmd # echo $? <Enter> 0 |
If grep(1)'s return code is 0, sfcfrmd daemon is running.
See
For details of ps(1) and grep(1), see the online manual page.
If the sfcfrmd daemon is not running, take corrective action according to errmsg. If the error message indicates "broken file", the file to cancel the suspension of the sfcfrmd daemon's startup might be broken. Reboot the system because this file is remade by booting the system.
If sfcfrmd daemon is running, no corrective action needs to be taken because it is thought the sfcfrmd daemon had been started before this file is broken.
Explanation
Startup of the sfcfrmd daemon has not been suspended.
Response
If the sfcfrmd daemon that is not being suspended is activated, execute the sfcfrmstart(8) command without the -f option.
