Starting and Stopping
---------------------

.. index:: app;app stop
.. index:: app;app start
.. index:: app;app status
.. index:: cluster;cluster run

The system application may be stopped with **app stop** and restarted with **app start**.


.. important::
   While services can be started across a cluster, they should not be stopped using
   the **cluster** command.
   
   In other words, do not run **cluster run <where> app stop <no arg>**
   
   For details on the cluster command and the ``<where>`` clause, see: :ref:`cli_commands`.

By default this is a non-blocking command, which means that the console prompt will be
available after running this command while processes that are a part of it are running.

It is possible to start or stop individual applications and/or processes by appending
the ``<application-name>[:<process-name>]``. The list of applications can be seen by
using the command **app status**.

For example, to start the process ``voss-queue``:

**app start voss-queue**

or

**app start voss-deviceapi:voss-queue**

It is possible to perform a blocking start by including ``blocking`` after start but 
before the ``<application-name>[:<process-name>]``.  For example:

**app start blocking**

**app start blocking voss-queue**

This will ensure that all background processes that are started by **app start**
will be completed before the console prompt is available.


.. |VOSS Automate| replace:: VOSS Automate
.. |Unified CM| replace:: Unified CM