Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

if
Note
Warning

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. See Check for operations in progress on the platform and wait for all operations to complete

To stop platform services:

  1. Stop the API on the API

...

  1. server or Monolithic server

    Code Block
    systemctl stop abiquo-tomcat
  2. Stop the UI on the API

...

  1. server or

...

  1. Monolithic server or dedicated UI server

    Code Block
    systemctl stop httpd
  2. Stop

...

  1. Remote services server

    Code Block
    systemctl stop abiquo-tomcat
  2. Stop the database on the

...

  1. Monolithic server or Database server or

...

  1. Datanode server.

    Code Block
    systemctl stop mariadb

...

  1. For a datanode configuration, you will also need to stop the Galera cluster. For more details, see Stop and start HA configuration

  2. Stop RabbitMQ (on the monolithic server or API Server or Datanode)

    Code Block
    systemctl stop rabbitmq-server
  3. V2V server -
    You do not need to stop anything because the BPM remote service is run on-demand only

  4. Stop monitoring server

    Code Block
    systemctl stop abiquo-delorean
    systemctl stop abiquo-emmett
    systemctl stop kairosdb
    systemctl stop cassandra
  5. On the monitoring server, check if Cassandra is really dead

    Code Block
    ps auwx | grep cassandra

    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.

    Code Block
    kill -9 12345

All processes on platform servers should now be halted.

...