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
Working of pstack action
When configured with this action, the agent framework captures the process stack or process stack with the process tree on entry point timeout. The agent framework takes a decision internally to capture the process tree along with the process stack. In the following cases, agent framework also captures the process tree along with the process stack for the process:
If the timed out entry point is implemented using script, the agent framework captures the process tree as well as the process stack.
If the timed out entry point is implemented in C/C++ and waits for some command to complete, the agent framework captures the process tree along with the process stack.
In all the other cases, the agent framework captures the process stack of the agent process. All the information related to process stack and process tree is captured in the FFDC_AGFWEP<ep_name>_A.log
file. This file contains the information of all the resources of the same type for which <ep_name> entry point has timed out. When file FFDC_AGFWEP<ep_name>_A.log
is full, the current data is moved to FFDC_AGFWEP<ep_name>_B.log
for backup.