03-15-2014 11:35 AM
I have setup custom script using applicaiton agent and custom script takes around 5 minutes to run, but i changed the monitoring interval to 500s, but resource is faulting after 2 minutes. Do you guys any idea?
Solved! Go to Solution.
03-16-2014 01:09 PM
You should change the "MonitorProgramTimeout" for the Process resource - see extract from bundled agents guide for Windows Process agent:
MonitorProgramTimeoutThe maximum wait time, in seconds, for theagent to receive a return value from themonitor routine. This attribute is ignored ifthe monitor program is not specified. Defaultis 30 seconds.
03-15-2014 03:24 PM
You will need to increase one or more of:
MonitorTimeOut
OnlineTimeOut
OfflineTimeOut
depending on which script takes 5 mins to run.
Mike
03-15-2014 08:04 PM
Sorry I was given wrong info. I 'm using process agent and it doesn't have online or offline time out. It is a windows Machine. Any attribute that I can change to make it happen ? Thanks in advance. I am trying it trhough GUi. Can I do it in command line ? If so, let me know.
03-16-2014 12:39 AM
does it take 5 mins to start or 5 mins to monitor ?
There are parameters in process agent which you can play around depending on what time your process is taking ..
Parameters like MonitorProgramTimeout, CleanProgramTimeout or StopProgramTimeout
refer to VCS bundled agents guide for details
http://sort-cdn.symantec.com/public/documents/sfha/6.0/windows/productguides/pdf/VCS_BundledAgents_60.pdf
If anything can be done from GUI, it can be done from command line as well though GUI will be easy to operate. Have you tried switches using "hares -modify" command ?
G
03-16-2014 06:53 AM
Thank you for quick reply. let me look at the doucment.
No, my resources takes 5 minutes to start, so I want my monitorInterval to more than 5 minuts. It if it less than 5 minutes, my resource will fault.
Since I'm using process agent I don't want to adjust any monitoring agent, I just want to modify my Process Resrouce which I have created.
OS - Windows
03-16-2014 01:09 PM
You should change the "MonitorProgramTimeout" for the Process resource - see extract from bundled agents guide for Windows Process agent:
MonitorProgramTimeoutThe maximum wait time, in seconds, for theagent to receive a return value from themonitor routine. This attribute is ignored ifthe monitor program is not specified. Defaultis 30 seconds.
03-16-2014 01:40 PM
Thank you very much Mike, I have changed my MitorProgramTimeout to 180 seconds, so when monitor comes for second check it wil be 360s and it is good enough for me to bring the resouce up, it didn't come up, but my process global agent mointorinterval was set it to 60s and it is faulting after 120s. What is happening is that if you have less than 60s, it will work, but if it is more than 60s, then you need to tweak the global process agent monitor interval. Did you get my point?
03-16-2014 02:52 PM
In opening post you said changed the monitoring interval to 500s - so did you set it back to 60 again?
Your MonitorInterval for the Process agent should be greater or equal to MonitorProgramTimeout.
Mike
03-16-2014 06:36 PM
Yes, I played around with your suggestions and worked fine. Thanks a loooooooooot guys.
You guys are always helpful.