29.2.3 Database Master is Down

A database master server exists for a multi-site implementation.

NOTE:Ensure to enable the SSH daemon on the appliance. To do this, browse https://<aafwebservername>:9443 and log in as a vaadmin. Click the System Services tab and start the SSH service.

You can perform the following steps to restore the database master:

NOTE:If you want to recover the Database Master server because of a failure, you must delete the server from the Cluster tab of the Administration portal, before re-joining the web server. To delete the server in the Cluster tab, see Configuring a Cluster. Delete the web server before re-joining.

  1. Log in as root to the server.

  2. Perform the following commands:

    1. Stop the Advanced Authentication server:

      systemctl stop aauth risk-service

    2. Remove the containers, network, and volumes which Advanced Authentication has created on the server:

      docker-compose -p aaf -f /opt/aauth/docker-compose.yml -f /opt/aauth/docker-compose.sles.yml down -v

      docker-compose -p risk -f /opt/risk/docker-compose.risk.yml down -v

    3. Start the Advanced Authentication server:

      systemctl start aauth risk-service

  3. Browse the URL https://<servername> in a web browser and rejoin the server.

    After joining the database server to the existing cluster, the database replication happens. If issues occur while joining the cluster configuration, ensure that the ports are accessible towards the Global Master and the database server. For more information, see Configuring the Firewall.