InfoScale™ 9.0 Cluster Server Agent Developer's Guide - AIX, Linux, Solaris, Windows
- Introduction
- Agent entry point overview
- About agent entry points
- Agent entry points described
- About the action entry point
- About the info entry point
- Considerations for using C++ or script entry points
- About the agent information file
- About the ArgList and ArgListValues attributes
- Creating entry points in C++
- About creating entry points in C++
- Syntax for C++ entry points
- Agent framework primitives
- Agent Framework primitives for container support
- Creating entry points in scripts
- About creating entry points in scripts
- Syntax for script entry points
- Agent framework primitives
- VCSAG_GET_ATTR_VALUE
- Agent Framework primitives with container support
- Example script entry points
- Logging agent messages
- Building a custom agent
- Building a script based IMF-aware custom agent
- Creating XML file required for AMF plugins to do resource registration for online and offline state monitoring
- Testing agents
- Static type attributes
- About static attributes
- Static type attribute definitions
- AdvDbg
- ArgList
- State transition diagram
- Internationalized messages
- Troubleshooting VCS resource's unexpected behavior using First Failure Data Capture (FFDC)
- Appendix A. Using pre-5.0 VCS agents
Debugging agent functions (entry points).
The LogDbg attribute indicates the debug severities enabled for the agent function or agent framework. Debug severities used by agent functions are in the range of DBG_1-DBG_21.
To enable debug logging, use the LogDbg attribute at the type-level.
To set debug severities for a particular resource-type:
hatype -modify <resource-type> LogDbg -add <Debug-Severity> [<Debug-Severity> ...]
To remove debug severities for a particular resource-type:
hatype -modify <resource-type> LogDbg -delete <Debug-Severity> [<Debug-Severity> ...]
To remove all debug severities:
hatype -modify <resource-type> LogDbg -delete -keys
Note that you cannot set debug severities for an individual resource.
To debug a specific agent's entry point, see the documentation for that agent. So for bundled agents, see the Bundled Agent's Reference Guide.
For example, if you want to log debug messages for the FileOnOff resource type with severity levels DBG_3 and DBG_4, use the hatype commands:
# hatype -modify FileOnOff LogDbg -add DBG_3 DBG_4 # hatype -display FileOnOff -attribute LogDbg TYPE ATTRIBUTE VALUE FileOnOff LogDbg DBG_3 DBG_4
The debug messages from the FileOnOff agent with debug severities DBG_3 and DBG_4 get printed to the log files. Debug messages from C++ entry points get printed to the agent log file (UNIX: $VCS_LOG/log/<resource_type>_A.log) and from script entry points will get printed to the HAD log file. An example line from the agent log file:
. . 2003/06/06 11:02:35 VCS DBG_3 V-16-50-0 FileOnOff:f1:monitor:This is a debug message FileOnOff.C:res_monitor[28]