PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment)

E.5.6 sfcfrmstart command

E.5.6.1 ERROR: sfcfrmstart: 0001: Permission denied

[Explanation]

Execution was attempted with other than super user permission.

[Action]

Retry execution with super user permission.

E.5.6.2 ERROR: sfcfrmstart: 0004: Cannot connect to cluster foundation

[Explanation]

Connection with the cluster control facility failed.

[Action]

Confirm that the cluster control facility has already been started.

E.5.6.3 ERROR: sfcfrmstart: 0005: Operation of management partition may be performed

[Explanation]

The management partition may be being used on either the self-node or another node.

[Action]

Wait for the operation of the management partition to end, and then retry.

E.5.6.4 ERROR: sfcfrmstart: 0006: Cannot allocate memory

[Explanation]

Memory could not be allocated. Memory of system is insufficient.

[Action]

Please check the state of a system, and wait for the termination of another process, or increase the swap space or real memory. After it and re-execute the command.

E.5.6.5 ERROR: sfcfrmstart: 0007: Read error on sfcfsrm.conf: errmsg

[Explanation]

Setting file sfcfsrm.conf could not be read.

[Action]

Perform management according to errmsg.

E.5.6.6 ERROR: sfcfrmstart: 0008: Read error on management partition

[Explanation]

Reading of the management partition failed.

[Action]

If the disk with the management partition is broken, see Section 20.5, " Backup of the management partition information." and Section 20.6, "Restoration of the management partition information." Check that a disk has not failed, and then contact local Customer Support.

E.5.6.7 ERROR: sfcfrmstart: 0009: Self-node does not belong to host group

[Explanation]

The self-node does not belong to a host group.

[Action]

Using the sfcsetup(1M) command, add the self-node to a host group.

E.5.6.8 ERROR: sfcfrmstart: 0010: Starting processing of sfcfrmd went wrong

[Explanation]

Start processing for sfcfrmd daemon failed.

[Action]

After confirming the state of the self-node and that sfcprmd daemon is available by using the like of the ps(1) command, contact local Customer Support.

E.5.6.9 ERROR: sfcfrmstart: 0011: sfcfrmd has already existed

[Explanation]

The sfcfrmd daemon has already been started.

[Action]

No particular countermeasure is necessary.

E.5.6.10 ERROR: sfcfrmstart: 0012: sfcsetup may not be performed

[Explanation]

As no setting is made to the management partition, the management partition cannot be accessed.

[Action]

Use the sfcsetup(1M) command to set up the management partition.

E.5.6.11 ERROR: sfcfrmstart: 0013: sfcprmd may not exist

[Explanation ]

The communication path to sfcprmd daemon cannot be established.

[Action]

After confirming the state of the self-node and that sfcprmd daemon is available by using the like of the ps(1) command, contact local Customer Support.

E.5.6.12 ERROR: sfcfrmstart: 0014: State check processing to sfcprmd went wrong

[Explanation]

State confirmation processing for sfcprmd daemon using several different daemons failed.

[Action]

After confirming the state of self-node and that sfcprmd daemon is available by using the like of the ps(1) command, contact local Customer Support.

E.5.6.13 ERROR: sfcfrmstart: 0015: Write error on management partition

[Explanation]

Write processing for the management partition failed.

[Action]

After confirming that no disk error occurred, contact local Customer Supports.

E.5.6.14 ERROR: sfcfrmstart: 0016: filename: open(2) error: errmsg

[Explanation]

File open processing for editing the sfcfsrm.vers file failed.

[Action]

Apply countermeasures as described in errmsg.

E.5.6.15 ERROR: sfcfrmstart: 0017: filename: write(2) error: errmsg

[Explanation]

File write processing for editing the sfcfsrm.vers file failed.

[Action]

Apply countermeasures as described in errmsg.

E.5.6.16 ERROR: sfcfrmstart: 0018: filename: rename(2) error: errmsg

[Explanation]

File rename processing for editing the sfcfsrm.vers file failed.

[Action]

Apply countermeasures as described in errmsg.