6.3 Console Error Messages

This section explains RMS error messages that are displayed on the console.

Messages are explained in the alphabetical order.

Note

Italic words indicated in messages are replaced with actual values, names, or character strings.

So, be careful when searching a message that begins with italic characters.

/etc/rc3.d/S99RMS: NOTICE: RMS configuration file not exist or not readable - RMS not starting.

Content:

RMS cannot be started, as RMS configuration file does not exist or cannot be read.

Corrective action:

If a system has not created any userApplication even once, no action is required even if this message is displayed. If this message is printed although userApplication was created, check the RMS configuration file.

1.doopenread WARNING
   WARNING: doopenread of mount-device (pid xxxx),
counter=x not done yet reporting status, waiting ...
2.doopenread NOTICE
    NOTICE: doopenread of mount-device (pid xxxx),
counter=x not done yet reporting status, waiting ...
3.dostat WARNING
    WARNING: dostat of mount-point (pid xxxx),
counter=x not done yet reporting status, waiting ...
4.dostat NOTICE
    NOTICE: dostat of mount-point (pid xxxx),
    counter=x not done yet reporting status, waiting ...

Content:

This message indicates a monitoring result of Fsystem resources that a system call, which is called for devices on the mountpoint, did not return within the specified time.

Corrective action:

When the counter value is within 1 to 3, a temporary I/O load may exist. In this case, no corrective action is required.

When the counter value is larger than 3, take following actions.

If a high load processing is ongoing at times when this message is displayed, review the operation and the configuration.
Tune the monitoring interval of file systems.
For Linux, prepare a disk device for monitoring.

Assertion condition failed.

Content:

If hvassert fails during use of -f or -F option, this message is printed and hvassert exits with the exit code 1.

Corrective action:

No action is required.

BEWARE: 'hvshut -f' may break the consistency of the cluster. No further action may be executed by RMS until the cluster consistency is re-established.This re-establishment includes restart of RMS on the shut down host. Do you wish to proceed?(yes = shut down RMS / no = leave RMS running).

Content:

This is a message to ask a user to execute hvshut -f or to exit. Choose "yes" to continue. Choose "no" to exit.

Corrective action:

Respond to the prompt.

Be careful as data consistency may be lost or data may be broken if hvshut -f is used.

BEWARE: the hvreset command will result in a reinitialization of the graph of the specified userApplication. This affects basically the RMS state engine only. The re-initialization does not mean, that activities invoked by RMS so far will be made undone. Manual cleanup of halfway configured resources may be necessary. Do you wish to proceed?(yes = reset application graph / no = abort hvreset).

Content:

This is a message to ask a user to execute hvreset or to exit. Choose "yes" to continue. Choose "no" to exit.

Corrective action:

Respond to the prompt.

Can't open modification file.

Content:

When hvmod is invoked with the -c option, it uses a temporary file. If this file cannot be opened for writing, this message is printed and hvmod exits with the exit code 1.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

Cannot start RMS! BM is currently running.

Content:

RMS is already running on the local host.

Corrective action:

Shut down the currently running version of RMS and restart.

Change dest_object to node.

Corrective action:

No action is required.

command1 cannot get list of resources via <command2> from hvcm.

Content:

The wizards rely on hvmod for dynamic modification. If there is a problem when the command command2 is executed, this message is printed and hvmod exits with the exit code 15.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

Command aborted.

Content:

A confirmation message may appear if the user attempts to proceed the command execution. This message is printed after the user selects not to proceed with a command to abort execution of the command.

Corrective action:

No action is required.

command: bad state: state.

Content:

If hvassert is performed by a state other than the valid state, this message is printed and hvassert exits with the exit code 1.

Corrective action:

Make sure that the state specified for hvassert is valid.

command: bad timeout: timeout.

Content:

If the timeout specified for the hvassert command is not a number, this message is printed and the command exits with the exit code 1.

Corrective action:

Specify a number for the timeout value of hvassert.

command: cannot open file filename.

Content:

The hvsend is used to send messages to an object in a resource graph. It can get the list of messages to send from a file. If this file cannot be opened, this message is printed and the hvsend command exits with the exit code 8.

Corrective action:

Make sure that the file filename exists.

command: cannot put message in queue

Content:

The command command relies on a message queue to transmit messages to the RMS base monitor. If this message transmission fails for some reason, this message is printed and the command exits with a non-zero code.

Corrective action:

This message may be output when the command is executed during RMS stop processing. In this case, execute the command again. If this message is output when the command is executed during other processing, record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

command: could not create a pipe

Content:

If the command command could not open the tty to be written to, this message is printed and the command exits with the exit code 7.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

command failed due to errors in <argument>.

Content:

When hvmod has been invoked, it uses hvbuild internally. If there is a problem with the execution of hvbuild, this message is printed and hvmod is aborted. The hvmod then exits with the exit code 1.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

command: failed due to undefined variable: local_host.

Content:

If the hvsend command is unable to find the value of the environment variable RELIANT_HOSTNAME, this message is printed and hvsend exits with the exit code 7.

Corrective action:

Make sure that RELIANT_HOSTNAME is defined.

<command> failed with exit code exitcode

Content:

The command command that was executed by the RMS command abnormally exited with the exit code exitcode.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

command: file already exists

Content:

When 'hvdisp -o' has been invoked by the user and the output file that has been specified as an argument already exists, this message is printed and hvdisp exits with the exit code 6.

Corrective action:

Specify a filename that does not already exist as the argument to 'hvdisp -o.'

command: message queue is not ready yet!

Content:

The command command relies on a message queue to transmit messages to the RMS base monitor. If this

message queue is not available for some reason, this message is printed and the command exits with the exit code 3.

Corrective action:

command: Must be super-user to issue this command

Content:

This message indicates that in order to run the command command, the user should have root privileges.

Corrective action:

Make sure that the user has root privileges before issuing the command.

command: RMS is not running

Content:

When the command command has been invoked, it checks to make sure that RMS is running. If RMS is not running, this message is printed and the command exits with the exit code 2.

Corrective action:

Make sure that RMS is running before invoking the different utilities.

Command timed out!

Corrective action:

No action is required.

Could not open localfile or could not create temporary file filename

Content:

If the localfile cannot be opened for reading or the temporary file filename cannot be opened for writing during hvrcp, this message is printed and hvrcp exits with the exit code 7.

Corrective action:

Check the permissions on the localfile to make sure that it is readable.

Could not restart RMS. RELIANT_PATH not set.

Content:

When the detector restarts RMS, it checks the value of the environment variable RELIANT_PATH. If the detector cannot get the value of this variable, this message is printed.

Corrective action:

Make sure that RELIANT_PATH is set to an appropriate value.

debugging is on, watch your disk space in /var

Content:

This message requests warns the user that the disk space in /varas the debug mode is on. It appears when debug mode is set to "on" by using hvutil -1.

Corrective action:

Make sure that the disk space in /var is sufficient.

Delay delay seconds.....

Content:

This is an informational message specifying the delay delay in seconds that has been provided by hvsend.

Corrective action:

No action is required.

DISCLAIMER: The hvdump utility will collect the scripts, configuration files, log files and any core dumps. These will be shipped out to RMS support. If there are any proprietary files you do not want included, please exit now. Do you want to proceed? (yes = continue / no = quit)

Content:

This message is printed on executing 'hvdump -E'.

The hvdump command collects following files: scripts, the RMS configuration file, log files, and core dumps. These files are provided to support RMS. When the specific files should not be provided, end the processing. The hvdump -E will collect information only when a user chooses "yes" to the following question: "Do you want to proceed?" (yes = continue / no = quit).

Corrective action:

Respond to the prompt.

DISCLAIMER: The hvdump utility will now collect the necessary information. These will be shipped to RMS support.

Content:

This message indicates that the hvdump command starts to collect the information.

Corrective action:

No action is required.

Dynamic modification is in progress, can't assert states.

Content:

The hvassert cannot be executed while dynamic modification is in progress.

Corrective action:

Execute the hvassert after dynamic modification is complete.

ERROR: Assertion terminated: RMS is shutdown

Content:

When RMS on the target node is stopped by hvshut (except -f option) while the hvassert is in process, this message is printed and the hvassert exits with the exit code 12.

Corrective action:

No action is required.

Error becoming a real time process: errorreason

Content:

The RMS base monitor runs as a real time process on Solaris (thus, the RMS base monitor is given a higher priority than other processes). If the base monitor cannot run asa real time process due to errorreason, this message is printed.

Corrective action:

Take the necessary action based on the cause. As for details on errorreason, see "Appendix A CF Reason Code Table."

ERROR: Forcibly switch request denied, the following node(s) are in LEFTCLUSTER state: nodes

Content:

When the hvswitch -f is executed to switch cluster applications forcibly, a request to forcibly switch cluster applications has been denied because CF remains in the LEFTCLUSTER state on some nodes nodes.

Corrective action:

Change the status of the nodes nodes to either of the following status and then start cluster applications forcibly.

CF is in the DOWN state and RMS is in the Offline state
CF is in the UP state and the RMS is in the Online state

For how to recover CF from the LEFTCLUSTER state, see "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."

ERROR: Forcibly switch request denied, unabele to kill node <node>

Content:

When the hvswitch -f is executed to switch cluster applications forcibly, a request to forcibly switch cluster applications has been denied because the node <node> without running RMS cannot be stopped forcibly.

Corrective action:

Manually stop the OS on the node <node> and then forcibly start cluster applications again.

To shut down the node forcibly, also review the configuration of the shutdown facility.

ERROR: Hvshut terminates due to timeout, some objects may still be Online.

Content:

This message appears upon timeout of hvshut command.

When the hvshut command is executed with either l/-s/-a option, some resources that are included in cluster applications may fail to stop.

Corrective action:

To prevent the timeout of the hvshut command, depending on your environment, change RELIANT_SHUT_MIN_WAIT, which is the global environment valuable of RMS, to larger value.

See

For details on RELIANT_SHUT_MIN_WAIT, see "RELIANT_SHUT_MIN_WAIT" in "Global environment variable" of the following manual below:

For PRIMECLUSTER 4.3A30 or later: "PRIMECLUSTER Reliant Monitor Services (RMS) with Wizard Tools Configuration and Administration Guide."

See "PRIMECLUSTER Reliant Monitor Services (RMS) with Wizard Tools Configuration and Administration Guide" for how to refer and change the RMS environment valuable.

Take either of following actions depending on with which option the hvshut command has been executed.

With -l option
Shut down the OS on the node on which the command has been executed, or stop the node forcibly.
With -s option
Shut down the OS on the target node of the command, or stop the node forcibly.
With -a option
Shut down the OS on all the nodes except a node on which RMS has ended normally, or stop the node forcibly.
With -L option
When the BM (base monitor) process does not stop on the node on which the command has been executed, execute the hvshut -f command to stop RMS forcibly. No action is required when the BM process stops.
With -A option
When the BM process does not stop on some nodes, execute the hvshut -f command on these nodes to stop RMS forcibly. No action is required when the BM process stops on all the nodes.

ERROR: Local SysNode must be specified

Content:

By using the hvswitch command to start a resource, you must specify the SysNode name of the node on which you execute the hvswitch command.

Corrective action:

Specify the SysNode name of the node on which you execute the hvswitch command and execute it.

Note

This message is output only for 4.3A40 or later.

ERROR: Maintenance Mode request cannot be processed. A userApplication is not in an appropriate state on remote hosts. See switchlog of remote hosts for details! - userApplication

Content:

Due to one of the following status below of the userApplication, the maintenance mode cannot start or finish other than the node on which the command has been executed.

Maintenance mode cannot start: userApplication is in Faulted state
Maintenance mode cannot finish: userApplication's status is different with the status just before the start of maintenance mode.

Corrective action:

After executing the corrective action below, start or finish the maintenance mode other than the node on which the command has been executed.

Maintenance mode cannot start: Clear the Faulted state of userApplication.
Maintenance mode cannot finish: Return the state of userApplication to the status jut before the start of maintenance mode.

ERROR: Maintenance Mode request cannot be processed. The state of the following objects is conflicting with the state of their parents. Leaving maintenance Mode now will cause a Fault to occur.

Content:

Maintenance mode cannot be terminated due to the following cause:
On some cluster node, the current state of userApplication is different from the state before entering maintenance mode.

Corrective action:

Terminate the maintenance mode after restoring the userApplication state to the state before entering maintenance mode.

Error setting up real time parameters: errorreason

Content:

If there is a problem while setting up the parameters for the RMS base monitor to run as a real-time process, this message is printed along with the reason errorreason for the problem.

Corrective action:

Take the necessary action based on the reason errorreason. As for details on errorreason, see "Appendix A CF Reason Code Table."

Error while starting up bm on the remote host <targethost>: errorreason

Content:

When hvcm is invoked with the -s option to start RMS on a remote host targethost, if there is a problem in starting up RMS on the remote host, this message is printed along with the reason for the problem errorreason.

Corrective action:

Take the necessary action based on the reason errorreason and reissue 'hvcm -s.' As for details on errorreason, see "Appendix A CF Reason Code Table."

Error while starting up local bm: errorreason

Content:

An error occurred while starting up the local bm.

Corrective action:

Take the necessary action based on the reason errorreason. As for details on errorreason, see "Appendix A CF Reason Code Table."

Failed to dup a file descriptor.

Content:

If RMS is unable to dup a file descriptor while setting the environment, this message appears.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

Failed to exec the hvenv file <hvenvfile>.

Content:

RMS was unable to exec the hvenv environment variable file hvenvfile.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

Failed to open pipe.

Content:

If RMS is unable to open a pipe for communication, this message is printed and RMS exits with the exit code 1.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

FATAL ERROR Could not restart RMS. Restart count exceeded.

Content:

When the detector tries to restart RMS, it records how many times RMS had to be restarted. If this count exceeds 3, then this message is printed.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

FATAL ERROR: Could not restart RMS. Restart script (script) does not exist.

Content:

When the detector is unable to restart RMS because the script script does not exist, this message is printed.

Corrective action:

Make sure that the script script exists.

FATAL ERROR: Could not restart RMS. Failed to recreate RMS restart count file.

Content:

When the detector tries to restart RMS, it records how many times RMS had to be restarted by writing the necessary information into a count file. If this file cannot be opened, the above message is printed.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

FATAL ERROR: RMS has failed to start!

Content:

As a cluster application has not been created, RMS cannot be started.

Corrective action:

Create the cluster application.

File open failed (path): errorreason.

Content:

If the file path, which is used by the hvassert command to communicate with the RMS base monitor, could not be opened, this message is printed along with the reason errorreason for this failure. The hvassert then exits with the exit code 5.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

File system of directory <directory> has no data blocks !!

Content:

An internal error occurred in RMS processing.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

Forced shut down on the local cluster host!

Content:

When the detector restarts the base monitor, it prints this message before proceeding.

Corrective action:

No action is required.

Fork failed.

Content:

If RMS is unable to fork a process, it prints this message and exits with the exit code 1.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

hvutil: Could not determine if RMS is running on <targethost>, errno exitcode

Content:

This message is printed when 'hvutil -A targethost' is called. This message indicates that the command failed to ascertain whether or not RMS is running on targethost. The exitcode indicates a value in /usr/include/sys/errno.h.

Corrective action:

Take action depending on the exitcode value.

hvutil: Could not determine IP address of <targethost>

Content:

The IP address of the cluster nodes <targethost> could not be detected.

Corrective action:

Add targethost of all cluster nodes into the /etc/hosts file.

hvutil: debug option must be a positive number for on, 0 for off.

Content:

When 'hvutil -L' has been invoked with a loglevel that is not 0 or 1, this message is printed and it exits with the exit code 6.

Corrective action:

Specify a valid logging level 0 or 1 for the command.

hvutil: Detector time period must be greater than minimumtime.

Content:

If the detector time period specified as an argument with 'hvutil -t' is less than minimumtime, hvutil is aborted and exits with the exit code 5.

Corrective action:

Invoke hvutil with a time period that is greater than minimumtime.

hvutil: Failed to allocate socket

Content:

Allocation of a socket that is used to communicate with a remote node failed.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

hvutil: Missing /etc/services entry for "rmshb"

Content:

An entry for the RMS heartbeat is missing in the /etc/services file.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

hvutil: Notify string is longer than mesglen bytes

Content:

A string for notification is too long.

Corrective action:

Set the string shorter than mesglen bytes.

hvutil: RMS is not running on <targethost>

Content:

This is printed when 'hvutil -A targethost' is called. This message indicates that RMS is not running on the specified node.

Corrective action:

No action is required.

hvutil: RMS is running on <targethost>

Content:

This is printed when 'hvutil -A targethost' is called. This message indicates that RMS is not running on the specified node.

Corrective action:

No action is required.

hvutil: The resource <resource> does not have a detector associated with it

Content:

The resource resource does not have a detector.

Corrective action:

Issue 'hvutil -N' on a resource that has a detector.

hvutil: The resource <resource> is not a valid resource

Content:

The resource resource is not a valid resource.

Corrective action:

Issue 'hvutil -N' on a resource that has a detector and is part of the resource graph.

hvutil: time period of detector must be an integer.

Content:

If the detector time period specified as an argument with 'hvutil -t' is not a number, hvutil is aborted and exits with the exit code 6.

Corrective action:

Make sure that the detector time period is an integer.

hvutil: Unable to open the notification file <path> due to reason: reason

Content:

The hvutil was unable to open the file path because of a reason reason.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

Invalid delay.

Content:

If the value of delay in sending messages, which is specified by hvsend, is less than zero, this message is printed.

Corrective action:

Provide a valid value for the delay.

It may take few seconds to do Debug Information collection.

Content:

As the hvdump command dumps the information regarding the resource graph, it prints this message while it is collecting the information.

Corrective action:

No action is required.

localfile filename does not exist or is not an ordinary file

Content:

If the localfile specified as an argument to hvrcp does not exist or if it is not a regular file, hvrcp exits with the exit code 7.

Corrective action:

Make sure that the localfile exists and is an ordinary file.

Name of the modification file is too long.

Content:

If the length of the name of the modification file (specified as an argument through the -f option) or the modification directives (specified via the -c option) is longer than 113 characters, this message is printed and hvmod exits with the exit code 4.

Corrective action:

Make sure that the arguments specified via -f and -c options are not too long.

NOTICE: failed to open/read device mount-device

Content:

The Fsystem resource state is other than online. While RMS executes open/read against GDS volume for checking the file system status, this message indicates that open/read is failed, as the volume is in the stopping state.

Corrective action:

The message is merely printed and has no influence to the work.

NOTICE: RMS died but has been successfully restarted, reconnecting

Content:

RMS has not been started.

Corrective action:

Start the RMS, as needed.

NOTICE: User has been warned of 'hvshut -A' and has elected to proceed.

Content:

When the user invokes 'hvshut -A' and chooses to execute the command in response to a confirmation message, this message is printed.

Corrective action:

No action is required.

NOTICE: User has been warned of 'hvshut -f -a' and has elected to proceed.

Content:

When the user chooses to execute the command 'hvshut -f -a', this confirmation message is printed.

Corrective action:

No action is required.

NOTICE: User has been warned of 'hvshut -L' and has elected to proceed.

Content:

When the user invokes 'hvshut -L,' and then continues to execute the command, this message is printed to confirm that 'hvshut -L' is being invoked.

Corrective action:

No action is required.

RELIANT_LOG_PATH is not defined

Content:

When the hvlogclean command is invoked without the -d option, it refers to the environment variable RELIANT_LOG_PATH, to locate the hvloginit script. If the value of the variable cannot be found, this message is printed and the command exits with exit code 6.

Corrective action:

Make sure that the environment variable RELIANT_LOG_PATH has not been unset and is set to the appropriate value.

RELIANT_PATH is not defined

Content:

When the hvlogclean command is invoked without the -d option, it refers to the environment variable RELIANT_PATH to locate the hvloginit script. If the value of the variable cannot be found, this message is printed and the command exits with the exit code 6.

Corrective action:

Make sure that the environment variable RELIANT_PATH is set to the appropriate value.

Remote host <hostname> is not Online.

Content:

This message appears when remote node hostname is not Online at execution of hvassert and the command exits with the exit code 1.

Corrective action:

Make sure that remote node is Online before executing hvassert.

Remote host does not exist - host.

Content:

This message appears when SysNode specified as 'hvassert -h host' does not constitute a part of resource graph and the hvassert exists with the exit code 10.

Corrective action:

Make sure that the remote node specified by hvassert exists.

Remote system is not online.

Content:

This message appears when hvassert is to be executed for an object on a remote node in which RMS is not running, and the hvassert exists with the exit code 10.

Corrective action:

Make sure that RMS is run on the remote system before executing hvassert.

Reset of RMS has been aborted.

Content:

When the user invokes hvreset, the hvreset command asks for a confirmation. If the answer is not yes, hvreset is aborted and this message is printed.

Corrective action:

No action is required.

Resource does not exist - resource.

Content:

This message appears when hvassert is to be executed for a resource that is not a part of RMS resource graph, and the hvassert exists with the exit code 10.

Corrective action:

Make sure that the resource exists before executing hvassert for a resource.

Resource is already online on target node

Content:

The start request of the resource with the hvswitch command was denied because the resource is already Online.

Corrective action:

No action is required.
Correct the specified resource if it is wrong, and then execute the hvswitch command again.

resource is not in state state.

Content:

When hvassert is to be executed for an object resource, hvassert detects that the resource is not in a state state. In this case, this message is printed and hvassert exits with the exit code 1.

Corrective action:

No action is required.

Resource type must be userApplication or gResource

Content:

hvswitch or hvutil requires a userApplication or a resource as its argument.

Corrective action:

Check the man page for hvswitch or hvutil for usage information.

Request cannot be processed. The following resource(s) are unexpectedly online

Content:

Since a resource is unexpectedly Online while some resources are being started, all the resources cannot be started or stopped on the node with the hvswitch or hvutil command.

Corrective action:

Restore the state of the resource that was unexpectedly Online to the last state before it becomes Online, and then start or stop the resource with the hvswitch or hvutil command.

RMS environment failure: Failed to set environment using hvenv. Default values for environment variables will be used.

Content:

RMS internal error.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

RMS environment failure: Failed to set environment variable <path> for command: <errno>.

Content:

RMS internal error.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

RMS environment failure: The following required variable is not defined in RMS environment:

Content:

One of the environment variables required by RMS is missing in hvenv.

Corrective action:

A critical error has occurred. Check if the environment definitions in the hvenv.* files are correct.

RMS environment failure: <function> failed with errno <errno>.

Content:

RMS internal error.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

RMS has failed to start! didn't find a valid entry in the RMS default configuration file "configfilename"

Content:

This message appears when the RMS default configuration file exists but does not contain a valid reference to a configuration to run.

Corrective action:

Either place a default configuration file name in the RMS default configuration file or put the current configuration name in a configuration that is to be activated.

RMS has failed to start! 'hvcm' has been invoked without specifying a configuration with the -c attribute, but with specifying other command line options. This may cause ambiguity and is therefore not possible. Please specify the entire commandline or use 'hvcm' without further options to run the default configuration.

Content:

No arguments for the -c option exist. This message appears when the user tries to start RMS without the -c option and specifying other commandline options.

Corrective action:

When using hvcm with the -c option, '-c configname' should be the last arguments on the command line. To use the default configuration, enter hvcm without any arguments to start RMS on the local node, and use 'hvcm -a' to start RMS on all the nodes.

RMS has failed to start! invalid entry in the RMS default configuration file "configfilename"

Content:

The user is not allowed to start RMS if the default configuration has invalid entry in the RMS default configuration file. The possible valid entries are 1. 'configname' or 2. 'hvcm options -c configname.' Refer to the hvcm man page for valid options in the second format.

Corrective action:

Remove all invalid entries in the RMS default configuration file. Refer the hvcm man page.

RMS has failed to start! multiple entries in the RMS default configuration file "configfilename"

Content:

The user is not allowed to start RMS if there are multiple entries in the default configuration file config.us.

Corrective action:

The user has to remove all the obscure entries in the RMS default configuration file and has to have only one valid configuration in it.

RMS has failed to start! RELIANT_HOSTNAME is not defined in the RMS environment

Content:

The environment variable RELIANT_HOSTNAME is not properly set.

Corrective action:

Ensure that the RMS environment variable RELIANT_HOSTNAME is not set erroneously to "" (null string) or is not explicitly unset in hvenv.local.

RMS has failed to start! the number of arguments specified at the command line overrides the internal buffer of the RMS start utility

Content:

This message appears when the number of arguments specified at the command line is more than the buffer capacity (= 30 command line arguments).

Corrective action:

Refer to the hvcm manual page for the correct syntax and usage.

RMS has failed to start! the number of arguments specified at the RMS default configuration file "configfilename" overrides the internal buffer of the RMS start utility

Content:

This message appears when the user tries to start the RMS using the RMS default configuration file but the number of arguments specified in the RMS default configuration file overrides the internal buffer of the RMS start command.

Corrective action:

Remove the unwanted arguments from the RMS default configuration file. Check the man page for hvcm to get the required options to start RMS.

RMS has failed to start! the options "-a" and "-s" are incompatible and may not be specified both

Content:

This message appears when the user tries to start RMS using the options -a and -s simultaneously.

Corrective action:

Check the man page for hvcm to get the format.

rms is dead

Content:

The hvrcp command checks whether the RMS base monitor is alive every 10 seconds. If it finds that it is not alive, it prints this message and exits with the exit code 1.

Corrective action:

Start the RMS on the host.

RMS on node node could not be shutdown with hvshut -A.

Content:

This message appears when the host cannot be shut down with hvshut -A.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

Root access required to start hvcm

Content:

To start RMS, the user must have the system administrator authority.

Corrective action:

Sending data to resource.

Content:

This message is printed when logging is turned on and data data is being sent to the object resource.

Corrective action:

No action is required.

Shutdown of RMS has been aborted.

Content:

When the user invokes 'hvshut -L,' the hvshut command asks for a confirmation. If the answer is no, 'hvshut -L' is aborted and this message is printed.

Corrective action:

No action is required.

Starting Reliant Monitor Services now

Content:

When RMS is starting up, this message is printed.

Corrective action:

No action is required.

Starting RMS on remote host host now

Content:

This message is printed when RMS is being started on the remote host host.

Corrective action:

No action is required.

startup aborted per user request

Content:

When RMS is being started up with the "-c" option, if the specified RMS configuration file is different from the entry in CONFIG.rms, a confirmation message is displayed to ask a user if a new RMS configuration should be activated. If the response is "no", this message is printed.

Corrective action:

No action is required.

systemctl command exited with retcode

Content:

If the systemctl command did not end normally while the hvcm command is executed, this message is output.

Corrective action:

Take the necessary action based on the retcode.

Note

This message is output only for 4.3A40 or later.

The command 'command' could not be executed

Content:

The execution of the command command failed.

Corrective action:

Check if the command is valid.

The command 'command' failed to reset uid information with errno 'errno' - 'errorreason'.

Content:

The execution of the command command failed to reset the effective user ID.

Corrective action:

The seteuid (2) failed due to the errno errno. Take an action depending on the errno value.

The command 'command' failed to set the effective uid information with errno 'errno' - 'errorreason'.

Content:

The execution of the command command failed to set the effective user ID.

Corrective action:

The seteuid(2) failed due to the errno errno.Take an action depending on the errno value.

The configuration file "<nondefaultconfig>" has been specified as option argument of the -c option, but the Wizard Tools activated configuration is "<defaultconfig>" (see <defaultconfig>). The base monitor will not be started. The desired configuration file must be re-activated by using PCS Wizard activation command.

Content:

The activated configuration is not the configuration that is specified by -c option. RMS cannot be started.

Corrective action:

Activate the configuration that is specified by the -c option. Start RMS.

The file 'filename' could not be opened: errormsg

Content:

If the file filename could not be opened because of errormsg while an RMS command is executed, this message is printed and hvdump exits with the exit code 8.

Corrective action:

Take the necessary action based on the errormsg.

The length of return message from BM is illegal (actuallength actual expectedlength expected).

Content:

When the hvassert command has received a return message from the base monitor, and when the length of the message is actuallength, not expectedlength, this message is printed and hvassert exits with the exit code 5.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

The state of RMS service is not active but state

Content:

When you start the base monitor of the node that the state of the systemd service of RMS (smawrrms.service) is not active, this message is output and the base monitor fails to start on this node.

Corrective action:

Remove causes that lead the state of the systemd service of RMS not to be active. After removing the causes, check if the state of the service is active. When the state still does not recover, record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

Note

This message is output only for 4.3A40 or later.

The state of RMS service is not online/degraded but state

Content:

When the SMF service of RMS is neither in the online state nor in the degraded state on a node, this message is printed and the base monitor on this node fails to start.

Corrective action:

Remove causes that lead the state of the SMF service of RMS not to be online or degraded. After removing the causes, check if the state of the service is online or degraded. When the state still does not recover, record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

The system call systemcall could not be executed: errormsg

Content:

If the systemcall could not be executed because of errormsg while an RMS command is executed, this message is printed and hvdump exits with the exit code 7.

Corrective action:

Take the necessary action based on the errormsg.

The use of the -f (force) flag could cause your data to be corrupted and could cause your node to be killed. Do not continue if the result of this forced command is not clear. The use of force flag of hvswitch overrides the RMS internal security mechanism. In particular RMS does no longer prevent resources, which have been marked as "ClusterExclusive", from coming Online on more than one host in the cluster. It is recommended to double check the state of all affected resources before continuing.
Do you wish to proceed ? (default: no) [yes, no]:

Content:

This is a message to ask a user to execute hvswitch -f or to exit. Choose "yes" to start cluster applications forcibly. Choose "no" to exit.

Corrective action:

Respond to the message.
Be careful as data consistency may be lost or data is broken if hvswitch -f is used. Make sure that the resource under the cluster application control to be forcibly started is not running on other node in an error mode.

Note

On PRIMECLUSTER 4.3A10 or later (Solaris) or PRIMECLUSTER 4.3A30 or later (Linux), following messages are additionally displayed before the final message line "Do you wish to proceed? (default: no) [yes, no]:"

IMPORTANT: This command may kill nodes on which RMS is not running in order to reduce the risk of data corruption!
Ensure that RMS is running on all other nodes. Or shut down OS of the nodes on  which RMS is not running.

This message indicates that nodes without running RMS may be forcibly stopped to decrease the risk of data corruption when cluster applications are forcibly started.

See

To forcibly start cluster applications, see "Notes on Switching a Cluster Application Forcibly" in "PRIMECLUSTER Installation and Administration Guide."

The userApplication is in the state Inconsistent on any node

Content:

The resource cannot be started or stopped with the hvswitch or hvutil command because the userApplication is Inconsistent on any node.

Corrective action:

The inconsistency of the userApplication must be resolved on all the nodes, and then start or stop the resource with the hvswitch or hvutil command.

The userApplication must be in the state Online, Offline or Standby on target node

Content:

The resource cannot be started or stopped because the userApplication is not Online, Offline, or Standby.

Corrective action:

The userApplication first needs to be brought to Online, Offline, or Standby before starting the resource with the hvswitch command.

The user has invoked the hvcm command with the -a flag on a host where RMS is already running, sending request to start all remaining hosts.

Content:

If hvcm is invoked with the -a flag, then RMS will be started on the other hosts in the cluster.

Corrective action:

No action is required.

timed out! Most likely rms on the remote host is dead.

Content:

While performing hvrcp, the command times out because the base monitor on the local host has not received a response from the base monitor on the remote host. The most probable reason is that the RMS on the remote host is stopped.

Corrective action:

Make sure that the RMS on the remote host is running.

timestamp: NOTICE: User has been warned of 'hvshut -f' and has elected to proceed.

Content:

When the user invokes 'hvshut -f,' and then continues to execute the command, this message is printed to confirm that 'hvshut -f' is being invoked.

Corrective action:

No action is required.

Too many asserted objects, maximum is the max.

Content:

Any attempt to assert on a number of objects that is greater than the maximum will print this message.

Corrective action:

Decrease the number of objects that are asserted to be fewer than maximum.

Unable to execute command: command

Content:

During hvmod, if the command command could not be executed, hvmod exits with the exit code 1.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

Unable to start RMS on the remote host using cfsh, rsh or ssh

Content:

RMS internal error.

Corrective action:

Record this message, collect investigation information, and contact field engineers. For details on collecting the investigation information, see "PRIMECLUSTER Installation and Administration Guide."

Usage: hvassert [-h SysNode] [-q] -s resource_name resource_state | [-h SysNode] [-q] -w resource_name resource_state seconds | [-h SysNode] [-q] -d resource_name state_detail [seconds]

Content:

Unless hvassert command is invoked in a correct way, this message is printed and the command exits with the exit code 6..

Corrective action:

Follow the usage specified in the message above.

Usage: hvcm [-V] [-a] [-s targethost] [-c config_file] [-h time] [-l level]

Content:

The hvcm command has been invoked in a way that does not conform to its expected usage.

Corrective action:

See the hvcm man page for correct usage.

Usage: hvconfig -l | -o config_file

Content:

The hvconfig command has been invoked in a way that does not conform to its expected usage. The command exits with the exit code 6.

Corrective action:

Follow the expected usage for the command.

Usage: hvdisp {-a | -c | -h | -i | -l | -n | -S resource_name [-u | -c] | -z resource_name | -T resource_type [-u | -c] | -u | resource_name | ENV | ENVL} [-o out_file]

Content:

The hvdisp command has been invoked in a way that does not conform to its expected usage. The command exits with the exit code 6.

Corrective action:

Follow the expected usage for the command.

Usage: hvdump {-g | -f out_file | -t wait_time}

Content:

The hvdump command has been invoked in a way that does not conform to its expected usage. The command exits with the exit code 6.

Corrective action:

Follow the expected usage for the command.

Usage: hvlogclean [-d]

Content:

The hvlogclean command has been invoked in a way that does not conform to its expected usage. The command exits with the exit code 6.

Corrective action:

Follow the expected usage for the command.

Usage: hvreset [-t timeout] userApplication

Content:

The hvreset command has been invoked in a way that does not conform to its expected usage. The command exits with the exit code 2.

Corrective action:

Follow the expected usage for the command.

Usage: hvshut {-f | -L | -a | -l | -s SysNode | -A}

Content:

The hvshut command has been invoked in a way that does not conform to its expected usage. The command exits with the exit code 6.

Corrective action:

Follow the usage specified above.

Usage: hvswitch [-f] userApplication [SysNode] | -p userApplication

Content:

When the hvswitch command has been invoked with an unknown option, or with three or more arguments, the command exits with the exit code 6.

Corrective action:

Follow the intended usage of the command.

Note

This message is output only for 4.3A30 or earlier.

Usage: hvswitch [-f] userApplication [SysNode] | [-f] resource SysNode | -p userApplication

Content:

When the hvswitch command has been invoked with an unknown option, or with three or more arguments, the command exits with the exit code 6.

Corrective action:

Follow the intended usage of the command.

Note

This message is output only for 4.3A40 or later.

Usage: hvutil {-a | -d | -c | -s} userApplication | -f [-q] userApplication | {-t n | -N string } resource | -L {level | display} resource | {-o | -u} SysNode | -l {level | display} | -w | -W | -i {all | userApplication} | -r | -m {on|off|forceoff} userApplication | -M {on|off|forceoff}

Content:

This message appears in any one of the following situations:

'hvutil -u' is invoked with more than 1 argument. Exit code 7.
'hvutil' is invoked without any options or arguments. Exit code 7.
'hvutil' is invoked with an invalid option. Exit code 7.
'hvutil -i' is invoked without an argument. Exit code 13.
'hvutil -r' is invoked with an argument. Exit code 14.
'hvutil {-w | -W}' is invoked with an argument. Exit code 9.
'hvutil -n' is invoked with NoConfirm as the only argument. Exit code 5.
'hvutil {-m | -M}' is invoked with an argument other than on, off, or forceoff. Exit code 16.
'hvutil -m' is invoked without an argument, or 'hvutil -M' is invoked with an argument. Exit code 16.

Corrective action:

Follow the intended usage of hvutil.

Note

This message is output only for 4.3A30 or earlier.

Usage: hvutil {-a | -d | -c | -s} userApplication | -f [-q] userApplication | {-f | -c} resource | {-t n | -N string } resource | -L {level | display} resource | {-o | -u} SysNode | -l {level | display} | -w | -W | -i {all | userApplication} | -r | -m {on|off|forceoff} userApplication | -M {on|off|forceoff}

Content:

This message appears in any one of the following situations:

'hvutil -u' is invoked with more than 1 argument. Exit code 7.
'hvutil' is invoked without any options or arguments. Exit code 7.
'hvutil' is invoked with an invalid option. Exit code 7.
'hvutil -i' is invoked without an argument. Exit code 13.
'hvutil -r' is invoked with an argument. Exit code 14.
'hvutil {-w | -W}' is invoked with an argument. Exit code 9.
'hvutil -n' is invoked with NoConfirm as the only argument. Exit code 5.
'hvutil {-m | -M}' is invoked with an argument other than on, off, or forceoff. Exit code 16.
'hvutil -m' is invoked without an argument, or 'hvutil -M' is invoked with an argument. Exit code 16.

Corrective action:

Follow the intended usage of hvutil.

Note

This message is output only for 4.3A40 or later.

WARNING: The '-L' option of the hvshut command will shut down the RMS software without bringing down any of the applications. In this situation, it would be possible to bring up the same application on another node in the cluster which *may* cause data corruption.
Do you wish to proceed ? (yes = shut down RMS / no = leave RMS running).

Content:

This message is printed when 'hvshut -L' is invoked. When a user chooses "yes", the command is executed. When a user chooses "no", the command is aborted.

Corrective action:

Choose "yes" to execute the command. Choose "no" to abort the command.

WARNING: The '-A' option of the hvshut command will shut down the RMS software without bringing down any of the applications on all hosts in the cluster.
Do you wish to proceed ? (yes = shut down RMS on all hosts / no = leave RMS running).

Content:

This message is printed when 'hvshut -A' is invoked. When a user chooses "yes", the command is executed. When a user chooses "no", the command is aborted.

Corrective action:

Choose "yes" to execute the command. Choose "no" to abort the command.

WARNING: There is an ongoing kill of cluster host(s) <nodes>. If the host <node> is needed in order to provide failover support for applications on the host(s) <nodes> then this hvshut command should be aborted.
Do you wish to proceed with the hvshut of host <node> (yes = shut down RMS / no = leave RMS running).

Content:

When 'hvshut' is invoked while a cluster node is in the process of being stopped, this message is printed. When a user chooses "yes", the command is executed. When a user chooses "no", the command is aborted.

Corrective action:

Choose "yes" to execute the command. Choose "no" to abort the command.

WARNING: You are about to attempt to resolve a SysNode 'Wait' state by telling RMS that the node in question (<sysnode>) has not actually gone down. This option will only work if, and only if, the cluster node and the RMS instance on that cluster node have been continuously up since before the 'Wait' state began. If the RMS instance on that cluster node has gone down and been restarted this option (hvutil -o) will not work and may cause the RMS instance on that node to hang. If the RMS instance on that node has gone down and been restarted, shut it down again (hvshut -f) and run the 'hvutil -u <sysnode>' command on this cluster host and then restart RMS on the other cluster node.

Content:

This message is printed when 'hvutil -o' is invoked. When a user chooses "yes", the command is executed. When a user chooses "no", the command is aborted.

Corrective action:

Choose "yes" to execute the command. Choose "no" to abort the command.

WARNING: Data corruption may occur, if the Sysnode referred to as option-argument of the '-u' option hasn't been completely deactivated.
Do you wish to proceed ? (default: no) [yes, no]:

Content:

This is printed when 'hvutil -u' is invoked. When a user chooses "yes", the command is executed. When a user chooses "no", the command is aborted.

Corrective action:

Choose "yes" to execute the command. Choose "no" to abort the command.