This section explains the sfcfrmd daemon error messages of the GFS Shared File System.
Explanation
sfcfrmd is not performed by superuser.
Response
Please start sfcfrmd by sfcfrmstart(8) command as a superuser.
Explanation
The direct module is performed.
Response
Start the sfcfrmd daemon by executing sfcfrmstart(8) with super user access privileges.
Explanation
Since there was injustice or file reading of pathname went wrong, sfcfrmd starting went wrong.
Response
Please check whether the file of pathname is set up correctly.
Explanation
The sfcfrmd daemon failed to start, because a working file sfile in /var/opt/FJSVsfcfs was broken.
Response
Make sure that /var/opt directory has a space by df(1) command. If there is not enough space, delete unnecessary files or move them to other file systems to increase space. Then re-start the node.
Explanation
The sfcfrmd daemon failed to start, because /etc/services has no entry of sfcfsrm or pathname is broken.
Response
Check if "sfcfsrm <Port number>/tcp" is added to the /etc/services file on all nodes in the cluster. If not, add it to the file. For details about the file definition, see services(5) of the online manual page.
If the setting above is right, pathname seems broken. Collect the diagnostic data with FJQSS, fjsnap, or pclsnap and contact field engineers.
Explanation
Since acquisition of a memory went wrong, sfcfrmd starting went wrong.
Response
Please check the state of a system, and wait for the end of other processes, or increase and reboot a swap domain.
Explanation
sfcfrmd starting went wrong.
Response
Please confirm whether the port number of sfcfsrm in the /etc/services is the same as the node starting the sfcfrmd daemon.
When the port number is different
After changes to the same port number as the node that has started the sfcfrmd daemon, please use sfcfrmstart(8) by the super user authority and start the sfcfrmd daemon.
When the port number is the same
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap in all nodes, and contact field engineers.
Explanation
sfcfrmd failed in reading and writing of pathname.
Response
Please check whether a setup as a management partition domain of the GFS Shared File System is right, or a disk operates normally.
Explanation
Since a cluster was not started, sfcfrmd starting went wrong.
Response
Please start a cluster.
Explanation
The CIP address registered in the management partition changed.
Response
By remaking and restoring the management partition, back the configuration of the partition to a previous one before a value of the CIP address changed. For details to remake and restore, see "9.6 Backup of the management partition information" and "9.7 Restoring of the management partition information."
Explanation
Connection with sfcprmd went wrong.
Response
Make sure that the sfcprmd daemon is running by ps(1) command (for example, "/bin/ps -e | grep sfcprmd".) If the sfcprmd daemon was stopped by the unload dependency script, restart sfcprmd by the load script ("/opt/SMAW/SMAWcf/dep/start.d/S81sfcfs load".) Otherwise, re-start the node.
If this message is output while the sfcprmd daemon is running, collect a core image of the daemon, and a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers. Restart the node where this problem occurred.
Explanation
Connection with sfchnsd went wrong.
Response
Make sure that the sfchnsd daemon is running by ps(1) command (for example, "/bin/ps -e | grep sfchnsd".) If the sfchnsd daemon was stopped by the unload dependency script, restart sfchnsd by the load script ("/opt/SMAW/SMAWcf/dep/start.d/S81sfcfs load".) Otherwise, re-start the node.
If this message is output while the sfchnsd daemon is running, collect a core image of the daemon, and a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers. Restart the node where this problem occurred.
Explanation
sfchnsd is not activated.
Response
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap in the node, and contact field engineers.
Explanation
A service port is not able to be acquired.
Response
Check if "sfcfsrm <Port number>/tcp" is added to the /etc/services file on all nodes in the cluster. If not, add it to the file. For details about the file definition, see services(5) of the online manual page.
Explanation
The maximum value of file descriptor generation was not able to be acquired.
Response
Please check the maximum value of a file descriptor.
Explanation
The node information for this node is not registered into the management partition special.
Response
Register the node information using sfcsetup(8) command.
