06-06-2013 11:22 PM
Getting the following error in engine_A.log:
2013/05/31 14:16:12 VCS INFO V-16-1-10307 Resource cvmvoldg5 (Owner: unknown, Group: lic_DG) is offline on dwlemm2b (Not initiated by VCS)
2013/05/31 14:16:14 VCS INFO V-16-6-15004 (dwlemm2b) hatrigger:Failed to send trigger for resfault; script doesn't exist
Solved! Go to Solution.
06-08-2013 08:38 PM
And you can setup debug for CVMVolDg resource type to monitor why it gets fault if the problem could be reproduced.
To turn on debug mode for the agent, you will need to edit the /opt/VRTSvcs/bin/CVMVolDg/cvmvoldg.lib, and uncomment one line.
from this:
# Uncomment the following to start debugging
# DEBUG="DEBUG"
to this:
# Uncomment the following to start debugging
DEBUG="DEBUG"
It is not necessary to restart the agent since this lib file is read every time the monitor is ran. By doing this, the agent will place more information in the engine log, which may give a better idea as to why the resources are timing out.
# haagent -stop CVMVolDg -force -sys <node name>
# haagent -start CVMVolDg -sys <node name>
06-07-2013 12:50 AM
Assuming cvmvoldg5 is of type CVMVolDg, then this message means the monitor entry point for CVMVolDg failed - I believe the monitor entry point does a "dd" read of the Volumes you specifiy in the CVMVolumes attribute, so probably a "dd" read to one of these volumes fail so you maybe had a SAN issue - you should check your system log to see of there are any I/O errors around this time.
Mike
06-08-2013 08:34 PM
Hi Edisson,
CVMVolDg monitoring can fault the CVMVolDg resources on a system if any of the following checks fail during monitoring:
06-08-2013 08:38 PM
And you can setup debug for CVMVolDg resource type to monitor why it gets fault if the problem could be reproduced.
To turn on debug mode for the agent, you will need to edit the /opt/VRTSvcs/bin/CVMVolDg/cvmvoldg.lib, and uncomment one line.
from this:
# Uncomment the following to start debugging
# DEBUG="DEBUG"
to this:
# Uncomment the following to start debugging
DEBUG="DEBUG"
It is not necessary to restart the agent since this lib file is read every time the monitor is ran. By doing this, the agent will place more information in the engine log, which may give a better idea as to why the resources are timing out.
# haagent -stop CVMVolDg -force -sys <node name>
# haagent -start CVMVolDg -sys <node name>
06-10-2013 04:02 AM
Thanks for the help mike and stinsong.