VCS agent not faulting resource after many timeout messages.
Article ID: 100001039
Updated On:
Resolution
ISSUE:
VCS agentnot faulting resource after many timeout messages.
PROBLEMDESCRIPTION:
Why isn't aresource Faulted when getting the following error:
VCS INFOV-16-2-13026 (sun1) Resource(ora_db02) - monitor procedure finished successfullyafter failing to complete within the expected time for (23) consecutivetimes
SOLUTION:
This is aninformational message. Since the FaultOnMonitorTimeouts variable is set to 4,the VCS monitor has to timeout 4 times in a row for the resource to bedetermined faulted.
The aboveinformational message means that the monitor timed out 1,2 or 3 consecutivetimes for 23 instances. However the resource never timed out 4 consecutive timeswhich is what is needed for the resource to be marked Faulted.
Here is thedefinition:
FaultOnMonitorTimeouts
Indicatesthe number of consecutive monitor failures to be treated as a
resourcefault. A monitor attempt is considered a failure if it does not
completewithin the time specified by the MonitorTimeout attribute.
When amonitor fails as many times as the value specified by this
attribute,the corresponding resource is brought down by calling the
3 cleanentry point. The resource is then marked faulted, or it is
restarted,depending on the value set in the Restart Limit attribute.
Issue/Introduction
VCS agent not faulting resource after many timeout messages.
Was this article helpful?
Yes
No
Powered by
