I get the following error message when installing a Machine Agent. How should I proceed?
Failed to find Premain-Class manifest attribute in /usr/share/appdynamics/machineagent.jar
Error occurred during initialization of VM
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
java -Dmetric.http.listener=true -jar machineagent.jarcommand.
Is there a way to install the AppDynamics database agent without the wizard, such as simply configuring the installation XML files? I want to monitor a client but I am having trouble when installing the agent. I cannot log in to the DB from outside the network and opening up the listener port on the DB for me right now is an issue. Is there a workaround?
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.
After PHP Agent installation there are a few cases when the Agent does not report to the Controller. Refer to the PHP Agent installation troubleshooting guide for the basic troubleshooting steps that verify the installation and place the Agent configuration files in the proper place.
Every deployment is different, so this task doesn't lend itself to a single master Puppet script maintained by AppDynamics. However, this Agent deployment using Puppet sample can help you get started on your own Puppet module.
The following documentation links will walk you through the requirements and steps for upgrading an agent.
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.
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.