The Mule command line tool can be used to start and stop a Mule application server. In this example, appServer1 is started.

${mule_home}/appServer1/bin/mule start

When the application server begins it's startup sequence, the following block will be displayed in the mule_ee.log.

************************************************************
* MuleESB and Integration Platform
* Version: 3.7.3 Build: b7977ef2
* Mulesoft, Inc.
* For more information go to
* http://www.mulesoft.com/mule-esb-enterprise
*
* Server started: 12/17/18 10:08 PM
* JDK: 1.8.0_74 (mixed mode)
* OS: Linux (2.6.32-754.6.3.el6.x86_64, amd64)
* Host: SLMSESB001.thrivent.com (10.1.2.3)
************************************************************

After Mule has started, each application in the application server will be deployed. After all of the applications are deployed, check the mule_ee.log to ensure that the instance is up and kicking.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Mule is up and kicking (every 5000ms)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

In this example, appServer1 is stopped.

${mule_home}/appServer1/bin/mule stop

If "Startup failed: Timed out waiting for a signal from the JVM" appears in the mule_ee.log, wait a few minutes, and check the mule_ee.log again, as there may be a subsequent attempt to "Starting the Mule Container...".