7.4.2 Error messages

rcqconfig -a node-1 node-2 . . . . node-n -g and -a cannot exist together.

Content:

The options -g and -a cannot be specified at a time.

Corrective action:

Specify with correct syntax definition, referring to the manual page.

Nodename is not valid nodename.

Content:

This error message indicates that the node name is not specified or longer than 31 bytes.

Corrective action:

Specify with correct syntax definition, referring to the manual page.

rcqconfig : failed to start

Content:

The error is reported if rcqconfig fails to start.

Corrective action:

Check the reason message that is printed at the same time with this message.

rcqconfig failed to configure qsm since quorum node set is empty.

Content:

Quorum state machine (qsm) is the kernel module that collects the states of the cluster nodes specified in

the quorum node set. This error message usually indicates that the quorum configuration does not exist.

Corrective action:

For syntax for quorum node, see the manual page of "rcqconfig" command.

cfreg_start_transaction:`#2813: cfreg daemon not present`

Content:

The rcqconfig routine has failed. This error message usually indicates that the synchronization daemon is not running on the node. The cause of error messages of this pattern may be that the cfreg daemon has died and the previous error messages in the system log or console will indicate why the daemon died.

Corrective action:

If the problem still remains, 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."

cfreg_start_transaction:`#2815: registry is busy`

Content:

The rcqconfig routine has failed. This error message usually indicates that the daemon is not in synchronized state or if the transaction has been started by another application. The cause of error message is that the registries are not in consistent state.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_start_transaction:`#2810: an active transaction exists`

Content:

The rcqconfig routine has failed. This error message usually indicates that the application has already started a transaction. If the cluster is stable, the cause of error messages is that different changes may be done concurrently from multiple nodes. Therefore, it might take longer time to commit.

Corrective action:

Re-execute the command. If the problem persists, the cluster might not be in a stable state. If this is the case,

unload the cluster by using cfconfig -u and reload the cluster by using cfconfig -l.

Too many nodename are defined for quorum. Max node = 64

Content:

This error message usually indicates that if the number of node specified are more than 64 for which the quorum is to be configured.

Corrective action:

Specify nodes that constitute the quorum within 64.

cfreg_get:`#2809: specified transaction invalid`

Content:

The rcqconfig routine has failed. This error message usually indicates that the information supplied to get the specified data from the registry is not valid (e.g. transaction is aborted due to time expiration or stop of synchronized daemon, etc.).

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_get:`#2819: data or key buffer too small`

Content:

The rcqconfig routine has failed. This error message usually indicates that the specified size of the data buffer is too small to hold the entire data for the entry.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

Cannot add node node that is not up.

Content:

This error message usually indicates that the user is trying to add a node whose state is not up in the NSM node space.

Corrective action:

Start up the down node or remove the node from the list which configures the quorum.

Cannot proceed. Quorum node set is empty.

Content:

This error message usually indicates that no node is specified to this option or there is no configured node.
The errors will also be output to standard error (stderr) when start of rcqconfig is failed.

Corrective action:

Designate the node to the option. Or, execute the command after configuring a quorum that contains the node.

cfreg_put:`#2809: specified transaction invalid`

Content:

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_put:`#2820: registry entry data too large`

Content:

The rcqconfig routine has failed. This error message usually indicates that the specified size data is larger than 28K.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

7.4.2.2 rcqconfig -s

stopping quorum space methods `#0408: unsuccessful`

Content:

The rcqconfig routine has failed. This error message usually indicates that there is no method specified.

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."

7.4.2.3 rcqconfig -x ignore_node-1 .... ignore_node-n

-g and -x cannot exist together.

Content:

This error message usually indicates that get configuration option (-g) cannot be specified with this option (-x).

Corrective action:

Specify with correct syntax definition, referring to the manual page.

Nodename is not valid nodename.

Content:

This error message indicates that the node name is not specified or longer than 31 bytes.

Corrective action:

Specify with correct syntax definition, referring to the manual page.

rcqconfig : failed to start

Content:

The error is reported if rcqconfig fails to start.

Corrective action:

Check the reason message that is printed at the same time with this message.

cfreg_start_transaction:`#2813: cfreg daemon not present`

Content:

Corrective action:

Restart the daemon using cfregd -r. If the daemon stops again, the problem cause can be identified from the error message displayed at that time. The most likely cause is the corruption of registry data.
If the problem still remains, 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."

cfreg_start_transaction:`#2815: registry is busy`

Content:

The rcqconfig routine has failed. This error message usually indicates that the daemon is not in synchronized state or if the transaction has been started by another application.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_start_transaction:`#2810: an active transaction exists`

Content:

Corrective action:

Re-execute the command. If the problem persists, the cluster might not be in a stable state. The error messages in the log will indicate the problem. If this is the case, unload the cluster using cfconfig -u and then reload using cfconfig -l.

Too many ignore node names are defined for quorum.Max node = 64

Content:

This error message usually indicates that if the number of ignore_node specified are more than 64.

Corrective action:

Specify a number of 64 or less for ignore_node.

cfreg_get:`#2809: specified transaction invalid`

Content:

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_get:`#2804: entry with specified key does not exist`

Content:

The rcqconfig routine has failed. This error message usually indicates that the specified entry does not exist.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_get:`#2819: data or key buffer too small`

Content:

The rcqconfig routine has failed. This error message usually indicates that the specified size of the data buffer is too small to hold the entire data for the entry.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

Can not add node node that is not up.

Content:

This error message usually indicates that the user is trying to add a node whose state is not up in the NSM node space.

Corrective action:

Start up the down node or remove the node from the list which configures the quorum.

Can not proceed. Quorum node set is empty.

Content:

This error message usually indicates that no node is specified to this option or there is no configured node.

Corrective action:

Designate the node to the option. Or, execute the command after configuring a quorum that contains the node.

cfreg_put:`#2809: specified transaction invalid`

Content:

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_put:`#2820: registry entry data too large`

Content:

The rcqconfig routine has failed. This error message usually indicates that the event information (data being passed to the kernel) to be used for other sub-systems) is larger than 32K.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_put:`#2807: data file format is corrupted`

Content:

The rcqconfig routine has failed. This error message usually indicates that the registry data file format has been corrupted.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cms_post_event: `#0c01: event information is too large`

Content:

The rcqconfig routine has failed. This error message usually indicates that the event information (data being passed to the kernel) to be used for other sub-systems) is larger than 32K.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

7.4.2.4 rcqconfig -m method_name-1 .... method_name -n

-g and -m cannot exist together.

Content:

This error message usually indicates that get configuration option (-g) cannot be specified with this option (-m).

Corrective action:

Specify with correct syntax definition, referring to the manual page.

Methodname is not valid method name.

Content:

This error message indicates that the node name is not specified or longer than 31 bytes.

Corrective action:

Specify with correct syntax definition, referring to the manual page.

rcqconfig : failed to start

Content:

The error is reported if rcqconfig fails to start.

Corrective action:

Check the reason message that is printed at the same time with this message.

cfreg_start_transaction:`#2813: cfreg daemon not present`

Content:

Corrective action:

If the daemon stops again, the problem cause can be identified from the error message displayed at that time. The most likely cause is the corruption of registry data.
If the problem still remains, 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."

cfreg_start_transaction:`#2815: registry is busy`

Content:

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_start_transaction:`#2810: an active transaction exists`

Content:

Corrective action:

Re-execute the command. If the problem persists, the cluster might not be in a stable state. Unload the cluster using cfconfig -u and then reload using cfconfig -l.

Too many method names are defined for quorum. Max method = 8

Content:

This error message usually indicates that if the number of methods specified is more than 8.

Corrective action:

Designate the number of methods within 8.

cfreg_get:`#2809: specified transaction invalid`

Content:

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_get:`#2804: entry with specified key does not exist`

Content:

The rcqconfig routine has failed. This error message usually indicates that the specified entry does not exist.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_get:`#2819: data or key buffer too small`

Content:

The rcqconfig routine has failed. This error message usually indicates that the specified size of the data buffer is too small to hold the entire data for the entry.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_put:`#2809: specified transaction invalid`

Content:

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_put:`#2820: registry entry data too large`

Content:

The rcqconfig routine has failed. This error message usually indicates that the event information (data being passed to the kernel) to be used for other sub-systems) is larger than 32K.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_put:`#2807: data file format is corrupted`

Content:

The rcqconfig routine has failed. This error message usually indicates that the registry data file format has been corrupted.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cms_post_event: `#0c01: event information is too large`

Content:

The rcqconfig routine has failed. This error message usually indicates that the event information (data

being passed to the kernel) to be used for other sub-systems) is larger than 32K.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

7.4.2.5 rcqconfig -d node-1 node-2 .... node-n

-g and -d cannot exist together.

Content:

This error message usually indicates that get configuration option (-g) cannot be specified with this option (-d).

Corrective action:

Specify with correct syntax definition, referring to the manual page.

Nodename is not valid nodename.

Content:

This error message indicates that the node name is not specified or longer than 31 bytes.

Corrective action:

Specify with correct syntax definition, referring to the manual page.

rcqconfig : failed to start

Content:

The error is reported if rcqconfig fails to start.

Corrective action:

Check the reason message that is printed at the same time with this message.

cfreg_start_transaction:`#2813: cfreg daemon not present`

Content:

Corrective action:

cfreg_start_transaction:`#2815: registry is busy`

Content:

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_start_transaction:`#2810: an active transaction exists`

Content:

Corrective action:

Re-execute the command. If the problem persists, the cluster might not be in a stable state. Unload the cluster using cfconfig -u and then reload using cfconfig -l.

Too many nodename are defined for quorum. Max node = 64

Content:

This error message usually indicates that if the number of node specified are more than 64 for which the quorum is to be configured.

Corrective action:

Specify nodes that constitute the quorum within 64.

cfreg_get:`#2809: specified transaction invalid`

Content:

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_get:`#2804: entry with specified key does not exist`

Content:

The rcqconfig routine has failed. This error message usually indicates that the specified entry does not exist.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_get:`#2819: data or key buffer too small`

Content:

The rcqconfig routine has failed. This error message usually indicates that the specified size of the data buffer is too small to hold the entire data for the entry.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_put:`#2809: specified transaction invalid`

Content:

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_put:`#2820: registry entry data too large`

Content:

The rcqconfig routine has failed. This error message usually indicates that the specified size data is larger than 28K.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cfreg_put:`#2807: data file format is corrupted`

Content:

The rcqconfig routine has failed. This error message usually indicates that the registry data file format has been corrupted.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.

cms_post_event: `#0c01: event information is too large`

Content:

The rcqconfig routine has failed. This error message usually indicates that the event information (data being passed to the kernel) to be used for other sub-systems) is larger than 32K.

Corrective action:

Unload the cluster using cfconfig -u and then reload using cfconfig -l.