Failed to find Premain-Class manifest attribute in /usr/share/appdynamics/machineagent.jar
Error occurred during initialization of VM
A. The error message shows that the Machine Agent jar was used as a Java Agent.
>java -javaagent:d:\AppDynamics\installs\3.5.6\MachineAgent\machineagent.jar -version
Failed to find Premain-Class manifest attribute in d:\AppDynamics\installs\3.5.6\MachineAgent\machineagent.jar
Error occurred during initialization of VM. Agent library failed to init: instrument
Verify the command that is being used to start the Machine Agent. Follow the documentation to Install the Standalone Machine Agent. Open a separate command prompt and start the Machine Agent using
java -Dmetric.http.listener=true -jar machineagent.jar command.
A. You do not necessarily have to install the Database Agent on the database server. The database agent can reside on any server as long as that server can communicate to the database host. See Database Visibility System Requirements.
A. After PHP Agent installation there are a few cases when the agent does not report to the Controller. Use the following article for basic troubleshooting steps to verify the installation and place the agent configuration files in proper place. PHP Agent installation troubleshooting guide.
A. Every deployment is different, so this task doesn't lend itself to one master Puppet script maintained by AppDynamics. However, here is a sample that can help you get started on your own Puppet module. Agent deployment using Puppet.
A. For iOS and Android, follow these steps. Upgrading Mobile Agents
A. The following documentation links will walk you through the requirements and steps for upgrading an agent.
A. This error message is normally caused by the presence of a duplicate jar file from a different version of the Analytic Agent.
It can occur when the user unzips a new version of their
machine-agent.zip file into the same directory where the older Machine Agent resides, creating a duplicate presence of the same jar files.
The solution is to first take a backup of the old agent, then delete or rename the Machine Agent, and then unzip the new
Analytics agent failed to connect to the controller registration endpoint.
A. This issue occurs when using a self-signed certificate for the Controller. The Analytics Agent uses a truststore for the JRE to validate the certificate of the connecting server. The truststore does not have self-signed certificates added to the store by default.