| PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Solaris(TM) 10 Operating System) |
|
Contents
Index
|
| Appendix A List of Messages | > A.2 The GFS Shared File System Daemon messages |
This section explains the sfcfrmd daemon error messages of the GFS Shared File System.
The sfcfrmd daemon is not performed by super user
Please start sfcfrmd daemon by sfcfrmstart(1M) command as a super user.
The direct module is performed.
Start the sfcfrmd daemon by executing sfcfrmstart(1M) with super user access privileges.
Since there was injustice or file reading of pathname went wrong, sfcfrmd daemon starting went wrong.
Please check whether the file of pathname is set up correctly.
The sfcfrmd daemon failed to start, because a working file sfile in /var/opt/FJSVgfs was broken.
Make sure that /var/opt directory has a space by df(1M) command and re-start the node.
The sfcfrmd daemon failed to start, because /etc/services has no entry of sfcfsrm or pathname is broken.
Check if sfcfsrm9200/tcp is added to the "/etc/services" file on all the cluster nodes. If it is not, add it to the file. For details about the file definition, see services(4) of the "Solaris X Reference Manual Collection"
If the setting above is right, pathname seems broken. Collect the diagnostic data with fjsnap and contact local Customer Support.
Since acquisition of a memory went wrong, sfcfrmd daemon starting went wrong.
Please check the state of a system, and wait for the end of other processes, or increase and reboot a swap domain.
The sfcfrmd daemon starting went wrong.
Collect the diagnostic data with "/etc/opt/FJSVgfs/bin/sfcsnap.sh -c output_dir" and fjsnap in all the nodes, and contact your local Customer Support.
The sfcfrmd daemon failed in reading and writing of pathname.
Please check whether a setup as a management partition domain of the GFS Shared File System is right, or a disk operates normally.
Since a cluster was not started, sfcfrmd daemon starting went wrong.
Please start a cluster.
The CIP address registered in the management partition changed.
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".
Connection with sfcprmd daemon went wrong.
Make sure that the sfcprmd daemon is running by ps(1) command (for example, "/usr/bin/ps -e | /usr/bin/grep sfcprmd".) If the sfcprmd daemon was stopped by the unload dependency script, restart sfcprmd daemon 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 fjsnap for troubleshooting information then contact your customer support engineers. Restart the node where this problem occurred.
Connection with sfchnsd daemon went wrong.
Make sure that the sfchnsd daemon is running by ps(1) command (for example, "/usr/bin/ps -e | /usr/bin/grep sfchnsd".) If the sfchnsd daemon was stopped by the unload dependency script, restart sfchnsd daemon 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 fjsnap for troubleshooting information then contact your customer support engineers. Restart the node where this problem occurred.
The sfchnsd daemon is not activated.
Collect the diagnostic data with "/etc/opt/FJSVgfs/bin/sfcsnap.sh -c output_dir" and fjsnap, and contact your local Customer Support.
A service port is not able to be acquired.
Check if sfcfsrm9200/tcp is added to the /etc/services file on all the cluster nodes. If it is not, add it to the file. For details about the file definition, see services(4) of the "Solaris X Reference Manual Collection".
The maximum value of file descriptor generation was not able to be acquired.
Please check the maximum value of a file descriptor.
The node information for this node is not registered into the management partition special.
Register the node information using sfcsetup(1M) command.
|
Contents
Index
|