Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

ONLINE|MONITOR TIMEDOUT

Created: 18 Mar 2013 • Updated: 29 Apr 2013 | 4 comments
This issue has been solved. See solution.

HI ALL ,

I see a resource state in ONLINE|MONITOR TIMEDOUT state.What is this state ?How to clear this state ?

 

regards ,

siva

Operating Systems:
Discussion Filed Under:

Comments 4 CommentsJump to latest comment

mikebounds's picture

If the monitor times out more times than set by the agent attribute FaultOnMonitorTimeouts (default of 4), then the resource is faulted and then the clean script is normally called to offline the resource.  As your resource is ONLINE, this could mean the clean failed or ManageFaults attribute is set to NONE so VCS takes no action on a resource fault.

To resolve you could:

  1. Look at the reason why your monitor is timing out to try and stop the monitor timing out
  2. Manually offline the resource and then clear the fault

Mike

 

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below

Venkata Reddy Chappavarapu's picture

In your case the resource is online state and the monitor entry point is timing out. It could be due to monitor entry point hung. You can check whatever script your monitor entry point runs, could be run withoiut any issues outside, and resolve any issue. Then you can probe the resource to sees if it can complete the monitor.

 

You can also try increasing the MonitorTimeout value for the resource type.

 

Regards,

Venkat

Venkata Reddy Chappavarapu,

Sr. Manager,

Information Availability Group (VCS),

Symantec Corporation

===========================

PS: If you are happy with the answer provided, please mark the post as solution. You

stinsong's picture

The status means the resource type monitor agent does not get return value within turnable parameter MonitorTimeout while the resource is online.

To clear the state, you may kill and restart the resource type of agent (e.g. Agent /opt/VRTSvcs/bin/NIC/NICAgent) and then probe the resource by command "hares -probe <resource name> -sys <hostname>"

shiv124's picture

Thanks for the replies.I corrected the resource which has the problem.The issue is fixed.

 

Regards,

 

siva

SOLUTION