6.2.3 ERROR Messages

Error (ERROR or FATAL ERROR) messages that are displayed during RMS wizard execution are explained.

ERROR: /opt/SMAW/bin/hvawsipalias: External command failed. exit=<exit_code> detail=<aws_command options>

Content:

This is a message indicating that the aws command <aws_command options> has ended abnormally with the exit code <exit_code> during network takeover in an AWS environment.

Corrective action:

Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, refer to "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."

ERROR: /opt/SMAW/bin/hvawsipalias: Invalid configuration file. file=<config>,KeyName=<KeyName>

Content:

This is a message indicating that required items are not set in the configuration file for network takeover in an AWS environment.

Corrective action:

If the cluster application is in the Faulted state, clear the Fault using the RMS main window or the -c option of the hvutil command.

After that, set the necessary items in the configuration file for network takeover in an AWS environment.

For how to set the configuration file for network takeover, refer to "Building the Cluster Application for Network Takeover" in "Part 4 AWS Environment" in "PRIMECLUSTER Installation and Administration Guide Cloud Services."

After updating the configuration file for network takeover, execute the hvawschkconf(8) command and make sure that the contents of the configuration file are correct.

If the value of RELIANT_HOSTNAME is changed by mistake, this message will be output and a resource failure will occur. In this case, correct it to the correct value.

For more information on RELIANT_HOSTNAME, refer to "Local environment variables" in "PRIMECLUSTER Reliant Monitor Services (RMS) with Wizard Tools Configuration and Administration Guide."

ERROR: /opt/SMAW/bin/hvawsipalias: Invalid configuration file. file=<config>,Mode=<Mode>

Content:

This is a message indicating that required modes (ROUTE, DNS, and ELASTIC) are not set in the configuration file for network takeover in an AWS environment.

Corrective action:

If the cluster application is in the Faulted state, clear the Fault using the RMS main window or the -c option of the hvutil command.

After that, set the mode for one of the architectural patterns: ROUTE, DNS, or ELASTIC in the configuration file for network takeover in an AWS environment.

After updating the configuration file for network takeover, execute the hvawschkconf(8) command and make sure that the contents of the configuration file are correct.

ERROR: /opt/SMAW/bin/hvawsipalias: IpAddress not found in the <file>.

Content:

This is a message indicating that the IpAddress is not found in a JSON format file <file> that updates DNS during network takeover in an AWS environment.

Corrective action:

If the cluster application is in the Faulted state, clear the Fault using the RMS main window or the -c option of the hvutil command.

For details on a record file (JSON format) to update DNS, refer to "Building the Cluster Application for Network Takeover" in "Part 4 AWS Environment" in "PRIMECLUSTER Installation and Administration Guide Cloud Services."

ERROR: /opt/SMAW/bin/hvawsipalias: Multiple KeyNames are defined. KeyName=<KeyName>

Content:

This is a message indicating that multiple KeyNames are defined for the same CF node name in the configuration file for network takeover in an AWS environment.

Corrective action:

If the cluster application is in the Faulted state, clear the Fault using the RMS main window or the -c option of the hvutil command.

Multiple KeyNames cannot be defined for the same CF node name in the configuration file for network takeover in an AWS environment.

After updating the configuration file for network takeover, execute the hvawschkconf(8) command and make sure that the contents of the configuration file are correct.

ERROR: /opt/SMAW/bin/hvawsipalias: The configuration file <config> does not exist.

Content:

This is a message indicating that the configuration file <config> does not exist during network takeover in an AWS environment.

Corrective action:

If the cluster application is in the Faulted state, clear the Fault using the RMS main window or the -c option of the hvutil command.

After that, create the configuration file for network takeover in an AWS environment.

For how to create the configuration file for network takeover, refer to "Building the Cluster Application for Network Takeover" in "Part 4 AWS Environment" in "PRIMECLUSTER Installation and Administration Guide Cloud Services."

After creating the configuration file for network takeover, execute the hvawschkconf(8) command and make sure that the contents of the configuration file are correct.

ERROR: /opt/SMAW/bin/hvazurenic: Failed to add secondary IP address <ipaddress>

Content:

This message indicates that an attempt to add a secondary IP address to a virtual machine network interface in the network takeover in an Azure environment failed.

Corrective action:

The Azure CLI cannot be executed.

The following settings may be incorrect.

-The Azure resource information in the hvazurenicconfig file is incorrect.

-The service principal role does not have the required privileges.

- Secondary IP address is already in use by another virtual machine.

ERROR: /opt/SMAW/bin/hvazurenic: Invalid configuration file. file=<config>

Content:

This is a message indicating that required items are not set in the configuration file for network takeover in an Azure environment.

Corrective action:

The definition file <config> may have the following incorrect setting.

Correct any errors.

- File not created

- Authority error

- Insufficient number of parameters

-The takeover IP address is not specified in IPv4.

ERROR: /opt/SMAW/bin/hvscsireserve preempt-abort failed. prekey is <prekey>

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR: /opt/SMAW/bin/hvscsireserve --read-keys failed. Return code <code>

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

No action is required.

ERROR: /opt/SMAW/bin/hvscsireserve --read-reservation failed. Return code <code>. stdout is :

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR: /opt/SMAW/bin/hvscsireserve --read-reservation succeeded, but cannot get key. stdout is :

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR: /opt/SMAW/bin/hvscsireserve reserve failed. key is <key>

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR: appOnlineOrWait: fork() failed: <errmsg>

Content:

Information message.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR Avoid data corruption and abort the umount action to prevent a failover

Content:

An internal error occurred in the RMSWT program.

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

ERROR: az login failed. AppID=<AppID>, TenantID=<TenantID>, CertPath=<CertPath>

Content:

This is a message indicating that authentication of the service principal failed during network takeover in an Azure environment.

Corrective action:

Check that the service principal authentication information (AppID, TenantID, CertPath) described in the configuration file for network takeover in an Azure environment is the correct combination.

The command result of the Azure CLI is output as a standard output to [note].

If the service principal authentication information (AppID, TenantID, CertPath) is correct but an error occurs, check the Azure environment based on the information of [note].

ERROR Cannot able to determine zpool version.

Content:

An internal error occurred in the RMSWT program.

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

ERROR Cannot create directory <mountpoint>.

Content:

This error message indicates that a directory to which a Filesystem is mounted cannot be created.

Corrective action:

Solaris
Check if a path in which a directory is created exists. If enough area exists, create a new directory.
Linux
When Gds resources are registered in the cluster application and the MonitorOnly attribute is set in Fsystem resources, check if the following message is output in the system log at the time of the Offline processing immediately before the cluster application.
```
ERROR: REASON: failed to execute script <OfflineScript> with resource 
<Fsystem resource name>: Exited with a non-zero code: code
```

If the above message is output, restart the system to recover it from the faulted state.

If the message is output under any condition other than the above, check if a path in which a directory is created exists. If enough area exists, create a new directory.

ERROR Cannot create symlink <mountpoint>.

Content:

An internal error occurred in the RMSWT program.

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

ERROR: cannot get any disk for Persistent Reservation in blockdevice

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

Check the following:

Whether Gds resources or Fsystem resources are included in the cluster application.
Whether there are no errors in the entries of /etc/fstab.pcl file (for Linux), or /etc/vfstab.pcl file (for Solaris).

When the resource failed and this message is displayed even without any problems with the above confirmation, collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."

ERROR cannot read alias file <alias_file>.

Content:

An internal error occurred in the RMSWT program.

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

ERROR Cannot recreate NFS symbolic link <mountpoint> to <entry>

Content:

An internal error occurred in the RMSWT program.

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

ERROR cannot remove existing directory <mountpoint> to make symbolic link <mountpoint>.

Content:

The existing directory <mountpoint> cannot be removed. A symbolic link <mountpoint> cannot be created.

Corrective action:

Check if the directory <mountpoint> can be removed. The directory cannot be removed when files and sub directories exist in it, for example.

ERROR cannot remove existing symbolic link <mountpoint>.

Content:

An internal error occurred in the RMSWT program.

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

ERROR: CF is not running.

Content:

This is a message indicating that CF is not running.

Corrective action:

[In an AWS environment]: Execute the hvawschkconf (8) command to check the configuration file for network takeover in an AWS environment after setting the initial configuration of PRIMECLUSTER.

[In an Azure environment]: Execute the hvazurechkconf (8) command to check the configuration file for network takeover in an Azure environment after setting the initial configuration of PRIMECLUSTER.

If CF is not set, refer to "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide" and set CF. If CF is already set, start CF.

For how to start CF, refer to "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."

ERROR: CF node name not found in the configuration file. file=<config>

Content:

This is a message indicating that the CF node name to be checked is not found in the configuration file for network takeover in an AWS environment or an Azure environment.

Corrective action:

[In an AWS environment]

The configuration file <config> for network takeover in an AWS environment is checked using the hvawschkconf (8) command based on the CF node name of the local node. Set the valid CF node name.

Use the cftool -l command to check the CF node name of the local node.

[In an Azure environment]

The configuration file <config> for network takeover in an Azure environment is checked using the hvazurechkconf (8) command based on the CF node name of the local node. Set the valid CF node name.

Use the cftool -l command to check the CF node name of the local node.

For how to set the configuration file for network takeover, refer to "Building the Cluster Application for Network Takeover" in "Part 5 Azure Environment" in "PRIMECLUSTER Installation and Administration Guide Cloud Services."

ERROR: check_getbdev: fork() failed: <errormsg>

Content:

Information message.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR: checkReservation <disk> <reservation_key> <option> failed

Content:

An internal error occurred in the RMSWT program.

Corrective action:

ERROR: "<command>" exited with code <state>

Content:

The command <command> exited with the code <state>.

Corrective action:

To take a corrective action, check why the command <command> exited with the code <state>.

ERROR: could not parse server name for mount point <mount>

Content:

An internal error occurred in the RMSWT program.

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

ERROR Create <ipaddress> on interface <interface> failed. Out of alias slots.

Content:

An internal error occurred in the RMSWT program.

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

ERROR: device <device> in /etc/fstab.pcl is not supported

Content:

This message indicates that the entered device name in /etc/fstab.pcl is not in the correct format.

Corrective action:

Enter any of the following formats of device name for /etc/fstab.pcl:

When using GDS
- /dev/sfdsk/<disk_class_name>/dsk/<volume_name>
Without using GDS
- /dev/disk/by-id/ name
- /dev/disk/by-path/ name
- LABEL=<file_system_label_name>
- UUID=<file_system_UUID>
- /dev/sd name

For details on the formats of available device name, see "Linux User's Manual" depending on the OS version to be used.

ERROR: Disk device for I/O fencing can not be found

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

Check the following:

Whether Gds resources or Fsystem resources are included in the cluster application.
Whether there are no errors in the entries of /etc/fstab.pcl file (for Linux), or /etc/vfstab.pcl file (for Solaris).

ERROR: doCheckReservation <option> failed. Return code <code>

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

ERROR: doopenread: fork() failed: <errormsg>

Content:

Information message.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR: dopopen: fork() failed: <errormsg>

Content:

Information message.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR: doRelease <option> failed. Return code <code>

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR: doReserve <option> failed. Return code <code>

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

When the resource failed after this message was output, collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."

ERROR: dostat: fork() failed: <errormsg>

Content:

Information message.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR e2fsck -p <device> failed with error code <code>

Content:

The e2fsck -p command failed when it was executed in the Online processing of an Fsystem resource.

<device>: The name of a device on which a file system is allocated

<code>: The return value of the e2fsck -p command

Corrective action:

An Fsystem resource failure does not occur
No corrective action is required.
An Fsystem failure occurred. Operations can continue after userApplications are switched
Use hvutil command to clear the Faulted state.
An Fsystem failure occurred. Operations cannot continue
Use hvutil command to clear the Faulted state, and then shut down all the RMS in which the faulty Fsystem resource is registered.
Follow the "Red Hat Enterprise Linux fsck/e2fsck message guide" to restore the file system.
After the file system is restored, start RMS and restart the operations.
If the file system cannot be restored by above actions, contact field engineers.

ERROR: Failed to access disk <disk>.

Content:

Access to the disk by the I/O fencing function failed.

Corrective action:

Check if there is a storage connection error or storage failure.

If the error remains unsolved, 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."

ERROR: Failed to check AWS resource ID. id=<ID>

Content:

This is a message indicating that the AWS resource ID described in the configuration file for network takeover in an AWS environment failed to be checked.

Corrective action:

Use the AWS Management Console to check if the value of the AWS resource ID is correctly described in the configuration file for network takeover in an AWS environment.

The command result of AWS CLI is output as a standard output to [note].

If the value of the AWS resource ID is correct but the command ends with error, check the AWS environment based on the information of [note].

Output example: When the resource ID does not exist in an AWS environment

[1.problem]
ERROR: Failed to check AWS resource ID. id=<ID>

[note]
An error occurred (InvalidNetworkInterfaceID.NotFound) when calling the DescribeNetworkInterfaces operation: The networkInterface ID 'eni-<id>' does not exist.
============================================================

ERROR: Failed to check Azure Resource Group. Resource Group=<value>

Content:

This is a message indicating that the resource group of the Azure resource group described in the configuration file for network takeover in an Azure environment failed to be checked.

Corrective action:

The command result of the Azure CLI is output as a standard output to [note].

Check the Azure environment based on the information of [note].

ERROR: Failed to check Azure resource ID. id=<ID>

Content:

This is a message indicating that the resource ID of the Azure virtual router described in the configuration file for network takeover in an Azure environment failed to be checked.

Corrective action:

Check on the Azure portal whether the resource ID of the Azure virtual router described in the configuration file for network takeover of the Azure environment is the correct value.

The command result of Azure CLI is output as a standard output to [note].

If the value of the resource ID of the Azure virtual router is correct but the command ends with error, check the Azure environment based on the information of [note].

Output example) When the resource ID does not exist in an Azure environment

<Resource_Group> refers to the Azure resource group name.

[1.problem]
ERROR: Failed to check Azure resource ID. id=<ID>

[note]
The Resource '<ID>' under resource group '<Resource_Group>' was not found.
============================================================

ERROR Failed to mount <Zname> on <Zmountpoint>. Return code <RetCode>.

Content:

Mounting of the data set <Zname> to the mount point <Zmountpoint> has failed.

Corrective action:

ERROR Failed to ping <nfsserver>

Content:

Communication with the NFS server <nfsserver> failed.

Corrective action:

Check if communication with the NFS server <nfsserver> is possible.

ERROR Failed to share <Zname>. <Output>. Return code <RetCode>.

Content:

Sharing of data set <Zname> has failed.

Corrective action:

ERROR: get SCSIdevice failed. opt is <option>. Return code <code>

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

Check the following:

Whether Gds resources or Fsystem resources are included in the cluster application.
Whether there are no errors in the entries of /etc/fstab.pcl file (for Linux), or /etc/vfstab.pcl file (for Solaris).

ERROR: getSCSIdevice failed. opt is <option>. Return code <code>

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

Check the following:

Whether Gds resources or Fsystem resources are included in the cluster application.
Whether there are no errors in the entries of /etc/fstab.pcl file (for Linux), or /etc/vfstab.pcl file (for Solaris).

ERROR hv_nfs-c/hv_nfs-v called without any mount point.

Content:

An internal error occurred in the RMSWT program.

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

ERROR <hv_nfs-c/u> cannot determine OldMountType.

Content:

An internal error occurred in the RMSWT program.

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

ERROR <hv_nfs-c/u> <mountpoint> already has local filesystem mounted on it.

Content:

Information message.

Corrective action:

No action is required.

ERROR <hv_nfs-c/u> <mountpoint> is a symbolic name and its target already has local filesystem mounted on it.

Content:

Information message.

Corrective action:

No action is required.

ERROR <hv_nfs-c/u> <mountpoint> is a symbolic name and its target already has NFS filesystem mounted on it.

Content:

Information message.

Corrective action:

No action is required.

ERROR <hv_nfs-c> <mountpoint> already has NFS filesystem mounted on it.

Content:

Information message.

Corrective action:

No action is required.

ERROR: Illegal variable in getReadKeys. disk is <disk>. opt is <option>

Content:

An internal error occurred in the RMSWT program.

Corrective action:

ERROR: Illegal variable. disk is <disk>. key is <key>. opt is <option>

Content:

An internal error occurred in the RMSWT program.

Corrective action:

ERROR: Illegal variable. disk is <disk>. opt is <option>

Content:

An internal error occurred in the RMSWT program.

Corrective action:

ERROR: Incorrect KeyName is set. KeyName=<KeyName>

Content:

This is a message indicating that an incorrect KeyName is set in the configuration file for network takeover in an AWS environment or an Azure environment.

Corrective action:

[In an AWS environment]

For KeyName described in the configuration file for network takeover in an AWS environment, describe the ID of up to 16 letters and numbers. KeyName is case-sensitive.

[In an Azure environment]

For KeyName described in the configuration file for network takeover in an Azure environment, describe the ID of up to 16 letters and numbers. KeyName is case-sensitive.

ERROR: Invalid configuration file. file=<config>

Content:

This is a message indicating that required items are not set in the configuration file for network takeover in an Azure environment.

Corrective action:

Set the necessary items in the configuration file for network takeover in an Azure environment.

ERROR: Invalid configuration file. file=<config>,KeyName=<KeyName>

Content:

This is a message indicating that required items are not set in the configuration file for network takeover in an AWS environment.

Corrective action:

Set the necessary items in the configuration file for network takeover in an AWS environment.

ERROR: Invalid configuration file. file=<config>, KeyName=<KeyName>

Content:

This is a message indicating that required items are not set in the configuration file for network takeover in an Azure environment.

Corrective action:

Set the necessary items in the configuration file for network takeover in an Azure environment.

ERROR: Invalid configuration file. file=<config>,Mode=<Mode>

Content:

This is a message indicating that required modes (ROUTE, DNS, and ELASTIC) are not set in the configuration file for network takeover in an AWS environment.

Corrective action:

Set the mode for one of the architectural patterns: ROUTE, DNS, or ELASTIC in the configuration file for network takeover in an AWS environment.

ERROR: Invalid configuration file. file=<config>, Mode=<Mode>

Content:

This is a message indicating that the required mode (ROUTE) is not set in the configuration file for network takeover in an Azure environment.

Corrective action:

Set ROUTE to the mode specified in the configuration file for network takeover in an Azure environment.

ERROR Invalid MAC Address <macaddr> for the interface <interface> Valid format is fld:fld:fld:fld:fld:fld where fld matches pattern "[0-9a-z][0-9a-z]"

Content:

The invalid MAC address is set in the /usr/opt/reliant/etc/hvipalias file.

Corrective action:

Set the valid characters for the MAC address in the /usr/opt/reliant/etc/hvipalias file.

See "Setting Up Resources" in "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)" or "PRIMECLUSTER Installation and Administration Guide (Linux)" for details.

ERROR: IP address does not match with Takeover network resource.

Content:

This message indicates that the IP address of hvazurenicconfig and the takeover IP address do not match in the network takeover of the Azure environment.

Corrective action:

Make sure the IP address specified in the definition file for network takeover in the Azure environment matches the IP address associated with the host name in the hvipalias file.

ERROR: key is <key>. opt is <option>. disk is <disk>. Return code <code>

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

No action is required.

ERROR Lost <mountpoint>, about to re-configure

Content:

Information message.

Corrective action:

No action is required.

ERROR Lost <ZfsMountPoint>, about to reconfigure ...

Content:

Information message.

Corrective action:

No action is required.

ERROR Lost <ZpoolName>, about to reconfigure ...

Content:

Information message.

Corrective action:

No action is required.

ERROR <mountpoint> cannot be a mount point.

Content:

A file system cannot be mounted on the mountpoint <mountpoint>.

Corrective action:

Check if the file system can be mounted on the mountpoint <mountpoint>.

ERROR <mountpoint> is not of type nfs.

Content:

An internal error occurred in the RMSWT program.

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

ERROR: Multiple KeyNames are defined. KeyName=<KeyName>

Content:

This is a message indicating that multiple KeyNames are defined for the same CF node name in the configuration file for network takeover in an AWS environment or an Azure environment.

Corrective action:

[In an AWS environment]

Multiple KeyNames cannot be defined for the same CF node name in the configuration file for network takeover in an AWS environment.

[In an Azure environment]

Multiple KeyNames cannot be defined for the same CF node name in the configuration file for network takeover in an Azure environment.

ERROR: Multiple modes are set to a single KeyName. KeyName=<KeyName>,Mode=<Mode1,Mode2>

Content:

This is a message indicating that multiple architectural pattern modes are set to a single KeyName in the configuration file for network takeover in an AWS environment.

Corrective action:

Multiple architectural pattern modes cannot be set to a single KeyName in the configuration file for network takeover in an AWS environment.

For the KeyNames paired in the standby configuration, specify the same architectural pattern mode.

ERROR: NIC name does not exist. NIC name=<value>

Content:

This is a message indicating that the NIC name described in the configuration file for network takeover in an Azure environment does not exist.

Corrective action:

Check on the Azure portal whether the NIC name of the Azure described in the configuration file for network takeover of the Azure environment is the correct value.

ERROR One or more ZFS file systems not mounted. Online processing of <ZpoolName> failed.

Content:

One or more ZFS files are not mounted. Online processing of ZFS storage pool <ZpoolName> has failed.

Corrective action:

ERROR One or more zfs mountpoint directories is mounted. <Output>. Cannot import zpool <ZpoolName>.

Content:

One or more ZFS mount point directories are mounted. ZFS storage pool <ZpoolName> can not be imported.

Corrective action:

This event occurs when the zfs data set on the ZFS storage pool <ZpoolName> is mounted by the settings of other than PRIMECLUSTER. Unmount the zfs date set on <ZpoolName>.

ERROR One or more zfs mountpoint directories is shared. <Output>. Cannot import zpool <ZpoolName>.

Content:

One or more ZFS mount point directories are shared. ZFS storage pool <ZpoolName> can not be imported.

Corrective action:

This event occurs when the zfs data set on the ZFS storage pool <ZpoolName> is shared by the settings of other than PRIMECLUSTER. Unshare the zfs date set on <ZpoolName>.

ERROR Only legacy ZFS mount points are supported.

Content:

An internal error occurred in the RMSWT program.

Corrective action:

ERROR: opt is <option>. disk is <disk>. Return code <code>

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

No action is required.

ERROR: popen: fork() failed: <errormsg>

Content:

Information message.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR: probing of device <mount> failed <errorno>

Content:

Information message.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR: Request rejected: userApplication is in Maintenance Mode! - <application>

Content:

The hvswitch was rejected because <application> is in Maintenance Mode.

Corrective action:

Bring the <application> out of Maintenance Mode, then execute the hvswitch.

ERROR: Resource Group does not exist. Resource Group=<value>

Content:

This is a message indicating that the resource group described in the configuration file for network takeover in an Azure environment does not exist.

Corrective action:

Make sure the Azure portal whether the resource group of the Azure described in the configuration file for network takeover of the Azure environment is the correct value.

ERROR Restart <command args>

Content:

Information message.

Corrective action:

No action is required.

ERROR: Return code <code>

Content:

This message indicates the processing state of I/O fencing function.

Corrective action:

No action is required.

ERROR: server <nfsserver> is not responding

Content:

Information message.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR Testing i/o on <mountpoint> failed.

Content:

I/O processing to the mounted Filesystem failed.

Corrective action:

Check if the mountpoint can be accessed.

ERROR: The certificate file <certificate_file_path> does not exist.

Content:

This is a message indicating that the certificate file <certificate_file_path> of the service principal does not exist during network takeover in an Azure environment.

Corrective action:

Place the certificate file of the service principal in the file path specified in CertPath described in the configuration file for network takeover in an Azure environment.

ERROR: The combination of Instance and its IP address is invalid. InstanceIPAddress=<VirtualMachineIPAddress>, InstanceID=<ResourceID>

Content:

This is a message indicating that the virtual machine IP address <VirtualMachineIPAddress> has not been allocated to the virtual machine <ResourceID> that configures the cluster on Azure.

Corrective action:

Check the combination of <ResourceID> and the IP address of the virtual interface <VirtualMachineIPAddress> on the Azure portal.

Set a virtual VirtualMachineIPAddress in the configuration file for network takeover based on the virtual machine.

ERROR: The configuration file <config> does not exist.

Content:

This is a message indicating that the configuration file <config> does not exist during network takeover in an AWS environment or an Azure environment.

Corrective action:

[In an AWS environment]

Create the configuration file for network takeover in an AWS environment.

[In an Azure environment]

Create the configuration file for network takeover in an Azure environment.

For how to create the configuration file for network takeover, refer to "Building the Cluster Application for Network Takeover" in "Part 5 Azure Environment" in "PRIMECLUSTER Installation and Administration Guide Cloud Services."

ERROR: The ENIID and Instance do not match. ENIID=<ENIID>, Instance-ID=<Instance-ID>

Content:

This is a message indicating that <Instance-ID> that configures the cluster and <ENIID> of the virtual interface do not match in the configuration file for network takeover in an AWS environment.

Corrective action:

Use the AWS Management Console to check the combination of <Instance-ID> and <ENIID> of the virtual interface.

Based on the instance, set ENIID in the configuration file for network takeover.

ERROR: The RMS file system /opt/SMAW/SMAWRrms is full. Proper RMS operation, including this detector can no longer be guaranteed! Please make space in the file system.

Content:

Information message.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR: The RMS file system /opt/SMAW/SMAWRrms is full. The detector can no longer function properly and the stat routine will report (perhaps incorrectly) ok, as long as the condition persists!

Content:

Information message.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR There are no interfaces defined for <host> <interface> in <ipconffile>.

Content:

This message indicates that the network interface <interface> for the host <host> does not exist in the /usr/opt/reliant/etc/hvipalias file.

Corrective action:

Check if the network interface <interface> is usable.

ERROR There is no address defined for <interface> in <hostsfile>.

Content:

This message indicates that the required IP address entry does not exist in the /etc/hosts file.

Corrective action:

Add the required IP address entry to the /etc/hosts file.

ERROR There is no address defined for <interfacename> in <hostsfile>.

Content:

This message indicates that the required node entry does not exist in the /etc/hosts file.

Corrective action:

Add the required node entry to the /etc/hosts file.

ERROR There is no entry of mount point <mount point> of type <value>.

Content:

This message indicates that no required entries for the file system to be mounted exist in the /etc/[v]fstab[.pcl] file.

Corrective action:

Add the required entries to the /etc/[v]fstab[.pcl] file.

ERROR There is no generic driver for <interfacename>.

Content:

An internal error occurred in the RMSWT program.

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

ERROR There is no interface <interface> in <path>, aborting startup.

Content:

This message indicates that the required takeover IP address does not exist in the /usr/opt/reliant/etc/hvipalias file.

Corrective action:

Add the required takeover IP address to the /usr/opt/reliant/etc/hvipalias file.

ERROR There is no interface <value> in /etc/hosts, aborting startup.

Content:

This message indicates that the required node entry does not exist in the /etc/hosts file.

Corrective action:

Add the required node entry to the /etc/hosts file.

ERROR There is no netmask or prefix defined for <host> <interface> in <ipconffile>.

Content:

This message indicates that the required Netmask entry (for IPv4) or the Prefix entry (for IPv6) does not exist in the /usr/opt/reliant/etc/hvipalias file.

Corrective action:

Add the required Netmask entry (for IPv4) or the Prefix entry (for IPv6) to the /usr/opt/reliant/etc/hvipalias file.

ERROR There is no or no valid netname for <interfacename> in <hostsfile>.

Content:

An internal error occurred in the RMSWT program.

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

ERROR There is no RMS entry for shared file system <mount point> in <path>.

Content:

This message indicates that no required entries for the file system to be mounted exist in the following files.

Solaris
/etc/dfs/dfstab[.pcl]
Linux
/etc/exports[.pcl]

Corrective action:

Add the required entries to the above files.

See "Setting Up Resources" in "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)" or "PRIMECLUSTER Installation and Administration Guide (Linux)" for details.

ERROR There is no RMS entry for <mountpoint> in <fstab>.

Content:

This message indicates that no required entries for the file system to be mounted exist in the <fstab> file.

Corrective action:

Add the required entries to the <fstab> file.

ERROR There is no RMS entry for <mountpoint> in <dfstab>.

Content:

This message indicates that no required entries for the file system to be mounted exist in the /etc/dfs/dfstab[.pcl] file (for Solaris) or the /etc/exports[.pcl] file (for Linux).

Corrective action:

Add the required entries to the /etc/dfs/dfstab[.pcl] file (for Solaris) or the /etc/exports[.pcl] file (for Linux).

ERROR There is no RMS entry for <ZfsMountPoint> in <Vfstab> for zpool <ZpoolName>.

Content:

This message indicates that there is no entry for the ZFS storage pool <ZpoolName> in the <Vfstab> file.

Corrective action:

Add necessary entries to the <Vfstab>file.

ERROR There is no script <path>/hv_<value>-<value>, returning FALSE.

Content:

An internal error occurred in the RMSWT program.

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

ERROR Timeout configuring <mountpoint>

Content:

The Online processing or the Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

When the processing time times out beyond the expected value, investigate the cause of timeout. If the problem cannot be identified, collect information for an investigation. Then, contact field engineers.

ERROR Timeout deconfiguring <mountpoint>

Content:

The Online processing or the Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout in <command>

Content:

An internal error occurred in the RMSWT program.

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

ERROR Timeout in hvexec during precheck phase.

Content:

An internal error occurred in the RMSWT program.

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

ERROR Timeout in hv_filesys-c

Content:

The Online processing or the Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout in hv_filesys-u

Content:

The Online processing or the Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout in hv_ipalias-c.

Content:

The Online processing or the Offline processing of a takeover network resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout in hv_ipalias-u.

Content:

The Online processing or the Offline processing of a takeover network resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout in hv_zfs-c

Content:

The Online processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout in hv_zfs-u

Content:

The Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout processing Fuser <mountpoint>

Content:

The Online processing or the Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout processing Fuser <ZfsMountPoint>.

Content:

The Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout processing ifadmin -d <ipaddress>.

Content:

An internal error occurred in the RMSWT program.

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

ERROR Timeout processing umount <mountpoint>

Content:

The Online processing or the Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout processing UmountFS <option>.

Content:

The Online processing or the Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout processing UmountFS <umountoptions> <target>

Content:

The Online processing or the Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout processing UmountFS <ZfsPoolName>.

Content:

The Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout processing ZfsFuser <ZpoolMountPoint>

Content:

The Online processing or the Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout processing zpool export <ZpoolName>

Content:

The Online processing or the Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout while importing <ZpoolName>.

Content:

The Online processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout while mounting <ZfsMountPoint>

Content:

The Online processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout while mounting zfs mounts for <ZpoolName>.

Content:

The Online processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout while processing Fuser <ZfsMountPoint>

Content:

The Online processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout while processing UmountFS -L <mountpoint>

Content:

The Online processing or the Offline processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout processing <fuser/lsof> -s <nfsserver> <mountpoint>

Content:

A script times out during unmount processing of <MountPoint>.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR Timeout while processing temporary mount

Content:

An internal error occurred in the RMSWT program.

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

ERROR Timeout while zpool import <ZpoolName>.

Content:

The Online processing of a file system resource times out.

Corrective action:

Check if the script timeout value and the expected value are the same. If these values are different, set the expected value.

ERROR: Undefined CF node name is set. CF node name=<CF>

Content:

This is a message indicating that an undefined CF node name is set in the configuration file for network takeover in an AWS environment or an Azure environment.

Corrective action:

[In an AWS environment]

Set the valid CF node name that configures the cluster in the configuration file for network takeover in an AWS environment. Use the cftool -n command to check the valid CF node name.

[In an Azure environment]

Set the valid CF node name that configures the cluster in the configuration file for network takeover in an Azure environment. Use the cftool -n command to check the valid CF node name.

ERROR: unknown interface <interface>

Content:

Information message.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.

ERROR Wrong file system type <Type> for <ZfsMountPoint> in <Vfstab>.

Content:

This message indicates that the type of the file system to be mounted is not configured as zfs in the <Vfstab> file.

Corrective action:

In the <Vfstab> file, change the file system type to zfs.

ERROR: xfs_repair <device> failed with error code <code>.

Content:

The xfs_repair command failed when it was executed in the Online processing of an Fsystem resource.

<device>: The name of a device on which a file system is allocated
<code>: The return value of the xfs_repair command

Corrective action:

An Fsystem failure occurred. Operations can continue after userApplications are switched
Use hvutil command to clear the Faulted state.
An Fsystem failure occurred. Operations cannot continue
Use hvutil command to clear the Faulted state, and then shut down all the RMS in which the faulty Fsystem resource is registered.
Then, restore the file system.
After the file system is restored, start RMS and restart the operations.
If the file system cannot be restored by above actions, contact field engineers.

ERROR zpool name cannot contain '/'.

Content:

The name of ZFS storage pool can not include "/".

Corrective action:

Set a correct name of ZFS storage pool in /etc/vfsatb.pcl.

FATAL: cannot get any disk for Persistent Reservation in diskclass <classlist>

Content:

Cannot retrieve disk for Persistent Reservation.

Corrective action:

FATAL ERROR: cannot get any disk for Persistent Reservation in diskclass <diskclass>

Content:

Failed to get any disk for Persistent Reservation.

Corrective action:

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

FATAL ERROR: exit because child process returned <lyingretries> times with signal <signal>

Content:

An internal error occurred in the RMSWT program.

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: shutting down RMS!

Content:

An internal error occurred in the RMSWT program.

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: <Resource> cannot allocate a memory for azpool_t structure.

Content:

This message indicates that the memory allocation has failed.

Corrective action:

Determine why OS memory is depleted resulting in memory allocation failures.

FATAL ERROR: <Resource> cannot initialize the cmdjob for zfs list.

Content:

An internal error occurred in the RMSWT program.

Corrective action:

FATAL ERROR: <Resource> cannot initialize the cmdjob for zpool list.

Content:

An internal error occurred in the RMSWT program.

Corrective action:

FATAL ERROR: <resource> could not open the hvgdconfig file <file>. This error must be corrected before RMS will successfully start!

Content:

An internal error occurred in the RMSWT program.

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: <resource> does not have an entry in the hvgdconfig file. This error must be corrected before RMS will successfully start!

Content:

An internal error occurred in the RMSWT program.

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: <Resource> does not have an entry for zpool name in the hvgdconfig file. This error must be corrected for RMS to start.

Content:

An internal error occurred in the RMSWT program.

Corrective action:

FATAL ERROR: The detection for unknown resource has been requested. shutting down RMS!

Content:

An internal error occurred in the RMSWT program.

Corrective action:

FATAL ERROR: The zfs detector (pid = <Pid>) could not allocate the context structure for the resource <Resource> because of malloc failure.

Content:

This message indicates that the memory allocation has failed.

Corrective action:

Determine why OS memory is depleted resulting in memory allocation failures.

FATAL ERROR: The zfs detector (pid = <Pid>) could not find detector configuration file <File> for the resource <Resource>.

Content:

An internal error occurred in the RMSWT program.

Corrective action: