Start or Stop the Controller

On this page:

You can start or stop the Controller and its database, and also check the Controller health from the Enterprise Console GUI or CLI.

About Starting or Stopping the Controller

The scripts to start and stop the Controller and other AppDynamics platform processes are located in the platform-admin/bin directory. Using the scripts, you can start the processes that comprise the platform individually or all at once.

Starting or stopping individually allows you to turn off data collection (by shutting down just the app server, for instance) while performing database operations.

To avoid the possibility of data corruption errors, be sure to stop the application server and database gracefully (that is, by using the stop scripts described on this page) before shutting off or rebooting the machine on which the Controller is running.

You can start and stop the Controller and Controller services on the Controller page in the GUI or with the following commands. When you start and stop the Controller, services and processes related to the Controller also start and stop, including the Reporting Service. If you use the GUI to start and stop the Controller, specify that you want to stop MySQL if you want to also stop the Controller Database.

If your Enterprise Console manages multiple platforms, you have to distinguish the Controller platform of interest when using the command line by using --platform-name <name_of_the_platform>.

For example:

platform-admin.sh start-controller-db [--platform-name <name_of_the_platform>]
platform-admin.sh start-controller-appserver [--platform-name <name_of_the_platform>] [--with-db]

To see all options, run platform-admin.sh --help from the command line. For more information, see Enterprise Console Command Line or Administer the Enterprise Console.

The Enterprise Console has a max wait time of 45 minutes when starting or stopping the Controller. You can set a timeout which exits the command and returns a failure by appending --args controllerProcessTimeoutInMin=<minutes> to the end of your start or stop command.

Start and Stop the Controller and Database

When using the Enterprise Console, starting or stopping the Controller will also start or stop the Reporting Service.

On Linux

To start the Controller on Linux, run this command:

platform-admin.sh start-controller-appserver --with-db

To stop the Controller on Linux:

platform-admin.sh stop-controller-appserver --with-db

On Windows

On Windows, the Controller processes are installed as a service, named the AppDynamics Application service and AppDynamics Database service.

Never stop the Controller services from the task manager. To stop and restart the AppDynamics processes, open an elevated command prompt (run as administrator) and run the scripts for starting and stopping the service.

To start the services, run this command:

platform-admin.exe cli start-controller-appserver --with-db

To stop the Controller services:

platform-admin.exe cli stop-controller-appserver --with-db

If you have uninstalled the Controller as a Windows service for any reason, use these scripts to stop and start the Controller: startController.bat and stopController.bat from an elevated command prompt (run as administrator).

Start and Stop the Controller App Server

On Linux

Start the app server by running this command:

platform-admin.sh start-controller-appserver

Stop the app server using this command:

platform-admin.sh stop-controller-appserver

On Windows

Run the following command in an elevated command prompt:

platform-admin.exe cli start-controller-appserver

Stop the app server using this command:

platform-admin.exe cli stop-controller-appserver

Start and Stop the Controller Database

On Linux

Start the database by running this command:

platform-admin.sh start-controller-db

Stop the database by running this command:

platform-admin.sh stop-controller-db

On Windows

Stop the database by running the following command in an elevated command prompt:

platform-admin.exe cli start-controller-db

Stop the database by running this command:

platform-admin.exe cli stop-controller-db

Check Controller Health

bin/platform-admin.sh check-controller-health

The command returns the status of the Controller and its uptime:

Controller status : HEALTHY; Started 6 seconds ago.