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 Stop the UI on the API Server or Monolithic Server or dedicated UI Server Stop Remote Services server Stop the database on the Monolithic Server or Database 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) 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 haltedsystemctl stop abiquo-tomcat
systemctl stop httpd
systemctl stop abiquo-tomcat
systemctl stop mariadb
systemctl stop rabbitmq-server
You do not need to stop anything because the BPM remote service is run on-demand onlysystemctl stop abiquo-delorean
systemctl stop abiquo-emmett
systemctl stop kairosdb
systemctl stop cassandra
ps auwx | grep cassandra
kill -9 12345