The following issues can occur:
- Agent has been created but is not active.
- Agent fails to restart on Red Hat Enterprise Linux
- Agent hangs during initialization
| Agent has been created but is not active
Explanation:
The Infrastructure Management Server is unable to connect to the local agent. This problem can occur when the agent is slow in initializing, the agent is not properly installed on the device, the server is not authorized to connect to the agent, or the agent version is higher than the server version.
User Response:
In the error message, click OK to add the agent to the list of agents. Ensure that the local agent appears in the Remote agent folder in the Administration Console. However, this action does not connect the agent. |
| Agent fails to restart on Red Hat Enterprise Linux
Explanation:
The local agent running on Red Hat Enterprise Linux 9.x fails to restart when the computer is restarted.
User Response:
There is no workaround for this limitation. However, run the following command to restart the agent manually: pw agent start |
| Agent hangs during initialization
Explanation:
If any agent has more than 300 Web transaction monitor instances, the agent might stop responding during initialization. (This is a known limitation.)
User Response:
Distribute the Web transaction instances across multiple agents. |