Problem:
App Agent log is empty, or nothing is reported to the Controller.
Common Solutions:
- If your agent is behind a network firewall or load balancer, open ports to enable communication between the agent and the Controller.
- Avoid installing an App Agent into a directory used by the application server, such as a Tomcat directory.
- Always install the Java Agent to a directory of its own, such as
\usr\local\agentsetup\appserveragent. - The AppDynamics folder is installed by the same user who owns the application process.
- The AppDynamics folder must have read and write permissions.
- Check for the following error in the application logs while installing the Java Agent. This error means that the Java Agent folder is corrupt. Install a new Java Agent folder.
-
Error opening zip file or JAR manifest missing : \usr\local\agentsetup\appserveragent\javaagent.jar
-
- Is the runtime directory writeable by the Java Agent?
- Check for network connectivity issues.
- If the agent is not able to connect to the Controller, the agent will disable itself. When the connection is available it will re-register again.
- Validate the application name, tier names, and node names. These are mandatory configuration parameters for an agent.
- Examine logs for errors such as the following:
Additional Information:
- Troubleshooting Agent Issues - Reporting and Connectivity
- How to resolve Java Agents not reporting
- Documentation: Troubleshooting Java Agent Issues
- Documentation: Connect the Controller and Agents
- Documentation: Dynamic Language Agent Proxy
