6.2.2 WARNING Messages

This section explains WARNING messages that are displayed during RMS wizard execution.

cannot grab mount lock for dostat() check_getbdev(), returning previous state

Content:

Information message.

Corrective action:

If this message is output repeatedly, multiple Fsystem resources may have the same mountpoint. Check multiple Fsystem resources and make sure they do not have the same mountpoint.

If multiple Fsystem resources do not have the same mountpoint but this message is still output repeatedly, check if any other error message is output. If so, perform the corrective action of that error message.

cannot unlock mount lock for dostat() check_getbdev()

Content:

Information message.

Corrective action:

If this message is output repeatedly, multiple Fsystem resources may have the same mountpoint. Check multiple Fsystem resources and make sure they do not have the same mountpoint.

dostat found <info> returning 0

Content:

Information message.

Corrective action:

No action is required.

WARNING: /etc/opt/FJSVsdx/bin/sdxiofencing -P -t all failed. class is <class>. 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.

WARNING: /etc/opt/FJSVsdx/bin/sdxiofencing -P -t slice failed. class is <class>. 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..

WARNING: Active disk in <class> not found

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.

WARNING Application <application> cannot be brought Online due to Application <application> being in <current state> state. <application> has LicenseToKillWait=yes set.

Content:

Information message.

Corrective action:

No action is required.

WARNING Application <application> cannot be brought Online due to Application <application> being in Faulted or Inconsistent state on <host>. <application> has LicenseToKillWait=yes set.

Content:

Information message.

Corrective action:

No action is required.

WARNING Application <application> cannot be brought Online due to Application <application> being in Online State. <application> belongs to the same set as <application> and has a higher priority.

Content:

Information message.

Corrective action:

No action is required.

WARNING Application <application> cannot be brought Online due to Application <application> being Online in maintenance mode. <application> belongs to the same set as <application> and has a higher priority.

Content:

Information message.

Corrective action:

No action is required.

WARNING Application <application> cannot be brought Standby due to Application <application> being in Online State. <application> belongs to the same set as <application> and has a higher priority.

Content:

Information message.

Corrective action:

No action is required.

WARNING Application <application> cannot be brought Standby due to Application <application> being Online in maintenance mode. <application> belongs to the same set as <application> and has a higher priority.

Content:

Information message.

Corrective action:

No action is required.

WARNING Application <application> cannot be brought Standby due to Application <application> going Online. <application> belongs to the same set as <application> and has a higher priority.

Content:

Information message.

Corrective action:

No action is required.

WARNING Attempt to create another mount point failed.

Content:

Information message.

Corrective action:

No action is required.

WARNING: Cannot allocate memory for zfs entry, current size = <Size> for <Value> entry. Cannot detect the zpool properly.

Content:

This message indicates that the memory allocation has failed.

Corrective action:

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

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

WARNING Cannot assign any interface to <interface>.

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

WARNING Cannot configure a basic interface <ipaddress> on <interface> without -s option.

Content:

Information message.

Corrective action:

No action is required.

WARNING Cannot find <ipaddress> on interface <interface>.

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

WARNING: Cannot find the legacy mount point <MountPoint> in vfstab[.pcl]. Cannot monitor this resource.

Content:

This message indicates that there are no entries necessary to mount the file system in the /etc/vfstab[.pcl] file.

Corrective action:

Add necessary entries to the /etc/vfstab[.pcl] file.

WARNING: Cannot find the zpool info from bdev field (<Bdev>) of mpinfo <MountPoint> in vfstab[.pcl]. Cannot monitor this resource.

Content:

This message indicates that the zpool name can not be found from the line including <Bdev> in the /etc/vfstab[.pcl] file.

Corrective action:

Refer to "Prerequisites" of "Creating Fsystem Resources" in "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)" and check the correct dataset name included in the /etc/vfstab[.pcl] file.

WARNING Cannot unconfigure <address> on basic interface <interface> without -s option.

Content:

Information message.

Corrective action:

No action is required.

WARNING: check reservation failed. disk is <disk>. opt is <option>

Content:

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

Corrective action:

No action is required.

WARNING <Command> called without any ZFS mount point name.

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

WARNING <Command> called without any zpool name.

Content:

An internal error occurred in the RMSWT program.

Corrective action:

WARNING Configuration of interface <interface> failed, undoing changes. Link may be down !

Content:

Information message.

Corrective action:

No action is required.

WARNING Could Not Reset Mac Address for <interface>

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

WARNING Could not set Mac Address <takeovermac> for <interface>

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

WARNING: disk in <class> not found

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.

WARNING: disk is <disk>. opt is <option>. counter is <counter>

Content:

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

Corrective action:

No action is required.

WARNING Ensuring only allowed applications continue to run, with respect to policy based failover management (LicenseToKill/AutoBreak), must be done manually, if required, by executing "hvswitch -p <application>", after <application> leaves maintenance mode!

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

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

WARNING Force export of zpool <ZpoolName> failed with code <RetCode>.

Content:

zpool export in <ZpoolName> has failed.

Corrective action:

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

WARNING hv_filesys-c 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."

WARNING hv_filesys-u 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."

WARNING hv_ipalias-c called without any interface name.

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

WARNING hvutil -m forceoff <application> failed with error code <return value> (<error output>). <application> will not be brought out of maintenance mode!

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

WARNING hvutil -m off <application> failed with error code <return value> (<output value>). <application> will not be brought out of maintenance mode!

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

WARNING No ping at all succeeded.

Content:

Information message.

Corrective action:

No action is required.

WARNING: Not enough field in zfs list output at line no <LineNo>.

Content:

An internal error occurred in the RMSWT program.

Corrective action:

WARNING: reserve failed. disk is <disk>. opt is <option>

Content:

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

Corrective action:

No action is required.

WARNING: Retry limit reached

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.

WARNING: Return code <code>. Trying again ...

Content:

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

Corrective action:

No action is required.

WARNING: Return code <code1>, <code2>. Trying again ...

Content:

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

Corrective action:

No action is required.

WARNING ScanVfstab called without second parameter.

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

WARNING The base interface <interface> is not yet configured. A virtual interface cannot be assigned on top of it!

Content:

An interface allocated for a takeover IP address is not yet configured. A virtual interface cannot be configured on this interface.

Corrective action:

Configure the interface allocated for the takeover IP address to be usable.

WARNING The file system <mountpoint> may not be unmounted.

Content:

Information message.

Corrective action:

No action is required.

WARNING The file system <mountpoint> was not unmounted.

Content:

Information message.

Corrective action:

No action is required.

WARNING The interface <interface> was already present, but it could not be re-configured successfully.

Content:

Information message.

Corrective action:

No action is required.

WARNING: The pool name <ZpoolName> for legacy mountpoint <MountPoint>, which is used during the configuration time, is different from the entry in vfstab[.pcl] file, <Bdev>. Use the one in the vfstab[.pcl].

Content:

Information message.

Corrective action:

No action is required.

WARNING To avoid a possible deadlock situation, Application <application> cannot be brought Online due to Application <application> already coming <intended state>. <application> has LicenseToKillWait=yes set.

Content:

Information message.

Corrective action:

No action is required.

WARNING Trouble with <interface>, recovering ...

Content:

Information message.

Corrective action:

No action is required.

WARNING Application <application> cannot be brought Online due to Application <application> being in Faulted State. <application> belongs to the same set as <application> and has a higher priority.

Content:

Information message.

Corrective action:

No action is required.

WARNING Application <application> cannot be brought Online due to Application <application> being still in Wait State. <application> belongs to the same set as <application> and has a higher priority.

Content:

Information message.

Corrective action:

No action is required.

WARNING Application <application> cannot be brought Online due to Application <application> going Online. <application> belongs to the same set as <application> and has a higher priority.

Content:

Information message.

Corrective action:

No action is required.

WARNING Application <application> cannot be brought Online due to Application <application> is probably going to start. <application> belongs to the same set as <application> and has a higher priority.

Content:

Information message.

Corrective action:

No action is required.

WARNING Application <application> cannot be brought Standby due to Application <application> being in Online State. <application> belongs to the same set as <application> and has lower or higher priority.

Content:

Information message.

Corrective action:

No action is required.

WARNING Application <application> cannot be brought Standby due to Application <application> going Online. <application> belongs to the same set as <application> and has lower or higher priority.

Content:

Information message.

Corrective action:

No action is required.

WARNING <application> could not determine its own AutoBreak value. Assuming a value of <break value> ...

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

WARNING <command> called without any application sequence.

Content:

Information message.

Corrective action:

No action is required.

WARNING <hv_ipalias-u> called without any ipname.

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

WARNING <interface> is already configured, but no hosts were successfully pinged.

Content:

Information message.

Corrective action:

No action is required.

WARNING <interface> is already configured, but not with the requested addresss IpAddress.

Content:

Information message.

Corrective action:

No action is required.

WARNING <interface> was already configured with a different address.

Content:

Information message.

Corrective action:

No action is required.

WARNING <path>/<config>.apps does not exist. No processing of application priorities is possible!

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

WARNING: doopenread of mount-device (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.

WARNING: 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.

WARNING: failed to ascertain share status for <mount> within <maxretry> try/tries

Content:

Information message.

Corrective action:

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

WARNING: failed to open/read <tempfile> within <maxretry> try/tries.

Content:

Information message.

Corrective action:

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

WARNING: failed to popen <mount> within <maxretry> try/tries.

Content:

Information message.

Corrective action:

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

WARNING: failed to popen <mount> within <retries> try/tries

Content:

Information message.

Corrective action:

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

WARNING: failed to stat <mount> within <maxretry> in try/tries.

Content:

Information message.

Corrective action:

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

WARNING: failed to stat <mount> within <retries> try/tries

Content:

Information message.

Corrective action:

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

WARNING: failed to write tempfile <file>, with return code <return>

Content:

Information message.

Corrective action:

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

WARNING: failed to write tempfile <tempfile> within <maxretry> try/tries

Content:

Information message.

Corrective action:

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

WARNING: If the major/minor device numbers are not the same on all cluster hosts, clients will be required to remount the file systems in a failover situation!

Content:

Information message.

Corrective action:

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

WARNING: ip addr add <ipaddress>/<netmask> failed (<errorcode>).

Content:

Failed to add an interface allocated for a takeover IP address.

Corrective action:

Configure the interface allocated for the takeover IP address to be usable.

WARNING: ip link set dev <interface> up failed (<errorcode>).

Content:

Failed to start an interface allocated for a takeover IP address.

Corrective action:

Configure the interface allocated for the takeover IP address to be usable.

WARNING: <mountpount>, counter=<retrycount> not done yet reporting status, waiting ...

Content:

Information message.

Corrective action:

No action is required.

WARNING: <resource > is mounted and the NFS server is not reachable, so returning offline because mounted read only or application is non-switchable or NFS server under RMS control.

Content:

Although the resource resource is mounted, it cannot reach NFS server. Detector has returned off line, as it is ReadOnly or switchover disabled application or the NFS server is under RMS control.

Corrective action:

This is the information output before Rfs resource returns offline. Although it is displayed immediately before switchover, no action is required.

WARNING: Root access is essential for most functionality!

Content:

The hvw command should be executed as a root user.

Corrective action:

Exit the hvw command and then execute the command again as a root user.

WARNING: stat of <mountpoint> failed

Content:

Information message.
This means that the stat() system call to <mountpoint> failed in the check processing of the Fsystem resource.

Corrective action:

When a resource failure has occurred after this message was output, contact field engineers.
In either of the following cases, this message might be output when RMS starts up, then no action is required because this does not affect other processes that are operated by the system.

<mountpoint> is under the mount point controlled by other Fsystem resource.
There is no directory of <mountpoint> in the system.

WARNING: status processing timed out, returning previous state <state>

Content:

Information message.

Corrective action:

No action is required.

WARNING: hvnfsrestart: The IpAddress <Ipaddress Resource> failed to reach the state Offline in a safe time limit of 180 seconds. This may be a potential problem later.

Content:

The IP address resource <IpAddress Resource> did not become Offline state within 180 seconds.

Corrective action:

Take following actions depending on the status of userApplications when before and after this message was output.

When user Applications, including Gls resources or takeover network resources, are normally in Offline state or Standby state.
No corrective action is required.
When userApplications are not in Offline state and an RMS error message is output.
Follow the RMS error message to take a corrective action.