On this page:
Start the Standalone Machine Agent Start the Standalone Machine Agent on RPM-based Linux Systems
Start the Standalone Machine Agent on Windows Start the Standalone Machine Agent on Mac OS X Stop the Standalone Machine Agent
Stop the Standalone Installed Using the Non-JRE Bundled Zip Archive
Stop the Standalone Machine Agent on RPM-based Linux Systems
Stop the Standalone Machine Agent on Windows Stop the Standalone Machine Agent on Mac OS X Related pages:
Standalone Machine Agent Configuration Properties Associate Standalone Machine Agents with Applications Installing the Machine Agent on a PHP Node
Starting the Standalone Machine Agent has been improved for Linux, Solaris, Windows, and Mac OS X:
Script for running the Standalone Machine Agent as a service
Script for launching the Standalone Machine Agent using the bundled JRE, instead of using
"java -jar machine-agent.jar"
Standalone Machine Agent
Note that the implements a shutdown hook, so issuing the kill command (or Ctrl+C) from the operating system causes the the agent to perform a graceful shut down.
Start the Standalone Machine Agent
Start the Standalone Machine Agent on RPM-based Linux Systems
Start the Agent Service
If you installed using the Linux RPM, start the Standalone Machine Agent as follows:
for SystemV systems:
% service appdynamics-machine-agent start
for sysD systems:
Use the Standalone Machine Agent service launcher as follows:
% systemctl start appdynamics-machine-agent
Required User Permissions
You do not need to run the Standalone Machine Agent from a root or administrator account, but if you want to use it with JVM Crash Guard on a monitored application running from a root or administrator account, the Standalone Machine Agent requires root or administrator privileges to look in the monitored application's JVM process and directory listings for crash files.
You also will need to run the Standalone Machine Agent with administrator or root privileges if you want to monitor networks or disks that are only available to the administrator or root user.
The user that runs the Standalone Machine Agent must have write privileges to the c and directories in the <machine_agent_home> directory.
onf logs
Start the Standalone Machine Agent on Linux and Solaris Systems
If you installed using the JRE bundled zip archive for Linux and Solaris, run the launcher as follows:
% <machine_agent_home>/bin/appdynamics-machine-agent start
Start the Standalone Machine Agent on Windows
Start the Agent Using the Windows Launcher
From a command shell, enter the following:
C:\> <machine_agent_home>\bin\machine-agent.cmd /agentProps -D<agent_configuration_property>
In a command line console, execute the machine-agent.cmd to start the Standalone Machine Agent manually. The following provides the usage parameters for the machine-agent.cmd along with an example.
Usage for machine-agent.cmd
> machine-agent.cmd /h
Usage: machine-agent.cmd [/h] [/javaHome:JAVA_HOME] [/agentProps -Dprop1 [-Xprop2...]]
Start the machine agent.
/h print command line options /javaHome:JAVA_HOME set java home for the agent
/agentProps props set system properties for the machine agent
properties should be separated by a space. Example:
/agentProps -Dstd.sys.prop=value -Xnonstd.sys.prop=other
Example of machine-agent.cmd
C:\> machine-agent.cmd /agentProps
"-Dappdynamics.controller.hostName=192.168.1.20"
"-Dappdynamics.controller.port=8090"
"-Dappdynamics.agent.applicationName=ACMEOnline"
Start the Agent as a Windows Service
In a command line console, execute the following command to start the Standalone Machine Agent as a Windows service:
Agent Configuration Properties containing an equal sign ( = ) must be enclosed in double quotes (" ") as shown below:
C:\> <machine_agent_home>\InstallService.cmd
If you want to start the service once it's already installed use Windows Services:
From Windows Services, click Appdynamics Machine Agent and click start. Start the Standalone Machine Agent on Mac OS X
Start the Agent as a Service using the Install Script
Edit and then save the <machine_agent_home>/com.appdynamics.machineagent.plist file to include system configuration properties, such
as -Dappdynamics.agent.applicationName=ACMEOnline in the STD_JAVA_PROPS string as follows:
<key>ProgramArguments</key>
<array>
<string>bash</string>
<string>${INSTALL_DIR}/bin/machine-agent</string>
<string>${STD_JAVA_PROPS}-D<system_property1>=<value1>
-D<system_property2>=<value2></string>
<string>${NON_STD_JAVA_PROPS}</string>
</array>
From the bash command line, execute the following command to add the Standalone Machine Agent as a service and then start the Standalone Machine Agent service:
> sh <machine_agent_home>/osx-install.sh
Start the Agent as a Mac OS X Service from the bash Command Line
You can pass system configuration properties, such as -Dappdynamics.agent.applicationName=A to the osx-install.sh script as follows:
CMEOnline
> sh <machine_agent_home>/osx-install.sh -D<system_property1>=<value1>
-D<system_property2>=<value2></string>
Start the Agent as a Service Using launchctl
After you have added the Standalone Machine Agent as a service, from the bash command line, execute the following command to start the Standalone Machine Agent service:
1.
2.
> sudo launchctl load -w <machine_agent_home>/com.appdynamics.machineagent.plist