Error Message

The following error is reported in the Engine_A.log at %VCS_HOME%/log path

VCS ERROR V-16-2-13066 Agent is calling clean for resource(%RESOURCE%) because the resource is not up even after online completed.  

This message indicates that VCS has reached its timeout threshold before the resource was able to start.

The reason why the resource has not yet started varies. Usually, the resource is having trouble starting outside of the cluster and is not directly related to a problem within VCS.

Increase the OnlineWaitLimit timeout attribute. This allows more time for the resource to start.

• If the problem is that the resource simply requires more time to start, increasing the OnlineWaitLimit may resolve the issue.
• If the resource continues to fail to start, review the logs for the resource, application or Operating system to determine the reason why the resource is not starting .

The value can be change from command-line interface using the below command:

hatype -modify OnlineWaitLimit

For example, to modify the OnlineWaitLimit for a MountV resource, below is the set of commands

haconf -makerw
hatype -modify MountV OnlineWaitLimit
haconf -dump -makero

 

The value can be change from VCS Java Console using the below steps.

For example, to modify the OnlineWaitLimit for a MountV resource

1) Highlight the MountV resource

2) On the right-pane, select the Properties tab on top and then click on Show All Attributes 

3) Scroll through the list of attributes to find OnlineWaitLimit and edit the value to desired value.

4)  Say Yes when prompted to make changes

5) Use the Edit option on the extreme right to allow a popup to be displayed. Enter the new value.

6) Once changes are made, hit OK. The newly made changes need to be updated in the cluster configuration. To commit these changes, select Save and Close the configuration as shown below

Note: The default value is usually 2. The number is a multiple of the monitoring interval, which is usually 60 seconds. The best value depends on how much time is required for the monitored resource to start.