To start or stop the Controller:

  • Linux users can use the Enterprise Console GUI or CLI.
  • MS Windows users can use the Enterprise Console GUI or Windows services.

To check the Controller health, Linux and MS Windows users can use the Enterprise Console GUI or CLI.

Scripts Used to Start or Stop the Controller

The scripts to start and stop the Controller and other AppDynamics platform processes are located in the platform-admin/bin directory for standalone or secondary HA Controllers. Using the platform-admin script, you can start the platform processes individually or all at once. 

To avoid the possibility of data corruption errors, be sure to stop the application server and database gracefully by using the stop scripts 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 from the command line. 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, to distinguish the Controller platform, you must use the command line for standalone or secondary HA Controllers and specify the --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> 
CODE

To see all options, run platform-admin.sh list-jobs --service controller --platform-name <platform-name> 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.

How to Start or Stop a Standalone or Secondary High Availability Controller

The commands below only apply to standalone and secondary HA Controllers. See Starting or Stopping a Primary Controller for information on how to start or stop primary Controllers.

Start and Stop the Controller App Server

  • When using the Enterprise Console, starting or stopping the Controller will also start or stop the Reporting Service.
  • You can only start or stop the Secondary Controller.
Start the Controller App Server

The start-controller-appserver command starts the database automatically.

Start the app server:

platform-admin.sh start-controller-appserver
BASH

Stop the Controller App Server

The stop-controller-appserver command does not stop the database.

Stop the app server:

platform-admin.sh stop-controller-appserver
BASH

When using Controller HA, you can add the secondary option to stop the secondary appserver:

platform-admin.sh stop-controller-appserver --secondary
BASH

Start and Stop the Controller Database

Start the Controller Database

Start the Controller database:

platform-admin.sh start-controller-db
BASH

Stop the Controller Database

Stop the Controller database:

platform-admin.sh stop-controller-db
BASH

How to Start or Stop a Primary Controller in High Availability Pairs

Use the following commands to start or stop primary Controllers in HA pairs. You must log in to the primary Controller host before running the scripts to start the controller.sh processes. 

  • You should disable auto-failover before restarting a primary Controller. Do not forget to reenable auto-failover afterward.
  • If you enabled auto-failover in the Enterprise Console, and you stopped the app server to update certifications, the Enterprise Console will trigger a failover if it takes longer than five minutes to update.
  • If you are using a combination of the Enterprise Console with the High Availability Toolkit (HATK), then you can start or stop the Controller using services.

Start and Stop the Controller

To start and stop the Controller on Linux:

bin/startController.sh
BASH

Start and Stop the Controller App Server

To start the app server, run this script from the Controller home:

bin/controller.sh start-appserver
BASH
To stop the app server, run this command:  
bin/controller.sh stop-appserver
BASH

Start and Stop the Controller Database

On Linux

To start the database, run this script from the Controller home:

bin/controller.sh start-db
CODE

To stop the database:  

bin/controller.sh stop-db
CODE

How to Check Controller Health


To check on the health of the Controller, run:

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


The following output shows the status of the Controller and its uptime:

Controller status : HEALTHY; Started 6 seconds ago.
CODE

To check on the health of the Controller, run:

bin\platform-admin.exe cli check-controller-health
CODE

The Powershell Execution Policy must be set correctly for the command to work. See https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.2.