Stop platform services

This section describes how to stop platform services on all servers.

Before you begin, Check for operations in progress on the platform and wait for all operations to complete.

If there are operations in progress, DO NOT STOP the platform services because this can cause serious issues with your platform.

To stop platform services:

Stop the API on the API server or Monolithic server
systemctl stop abiquo-tomcat
Stop the UI on the API server or Monolithic server or dedicated UI server
systemctl stop httpd
Stop Remote services server
systemctl stop abiquo-tomcat
Stop the database on the Monolithic server or Database server or Datanode server.
For a datanode configuration, you will also need to stop the Galera cluster. For more details, see Stop and start HA configuration
Stop RabbitMQ (on the monolithic server or API Server or Datanode)
V2V server -
You do not need to stop anything because the BPM remote service is run on-demand only
Stop monitoring server
On the monitoring server, check if Cassandra is really dead
Get the process number for Cassandra (the first number in the output of the previous command), and kill it. In this example, Cassandra is process 12345.

All processes on platform servers should now be halted.