2. Starting, Stopping, and Restarting Tower

Ansible Tower ships with an admin utility script, ansible-tower-service, that can start, stop, and restart all Tower services running on the current single Tower node (including the message queue components, and the database if it is an integrated installation). External databases must be explicitly managed by the administrator. The services script resides in /usr/bin/ansible-tower-service and can be invoked as follows:

[email protected]:~$ ansible-tower-service restart


In clustered installs, ansible-tower-service restart does not include PostgreSQL as part of the services that are restarted because it exists external to Tower, and because PostgreSQL does not always require a restart. Starting in 3.7, use systemctl restart ansible-tower to restart services on clustered environments instead. Also you must restart each cluster node for certain changes to persist as opposed to a single node for a localhost install. For more information on clustered environments, see the Clustering section.

You can also invoke the services script via distribution-specific service management commands. Distribution packages often provide a similar script, sometimes as an init script, to manage services. Refer to your distribution-specific service management system for more information.


When running Tower containerized in OpenShift, do not use the ansible-tower-service script. Restart the pod using OpenShift instead.