VMmanager Knowledge Base
en En
es Es
Your feedback is an opportunity for improvement!
Take part in the survey and contribute to the development of the ISPsystem ecosystem.
Take the survey

Disabling high availability

This article contains instructions on how to manually disable high availability (HA). This may be required, for example, if the cluster storage becomes corrupted and disabling high availability in the standard way via the web interface does not work.

There are potential risks involved in altering a database. We do not recommend making manual edits to the database, as it can disrupt the correct operation of the platform.

Create a backup of the platform before performing any actions with the database.

To disable high availability:

  1. Connect to the server with the platform via SSH.
  2. Connect to the database:

    docker exec -it mysql bash -c "mysql isp -p\$MYSQL_ROOT_PASSWORD"
  3. Get the cluster node IDs:

    select n.id as node_id,n.name as node_name from vm_node n left join vm_cluster v on n.cluster=v.id where v.ha_enabled=1 and v.id=<Cluster_ID>;
  4. Disable the HA activity indicator:

    update vm_cluster set ha_enabled=false where id=<Cluster_ID>;
  5. Disconnect from the database:

    \quit
  6. Connect to the vm_box container:

    docker exec -it vm_box bash
  7. Disable HA-agent and corosync services on the nodes. Run the specified commands for each node in turn:

    vssh <Node_ID> 'systemctl stop ha-agent && systemctl disable ha-agent'
    
    vssh <Node_ID> 'systemctl stop corosync && systemctl disable corosync'
    Comment
  8. Check the statuses of the VMs on the nodes using the virsh utility. Make sure that the same VM is not running on two nodes at the same time:

    virsh list --all
The article was last updated on 02.04.2025. The article was prepared by technical writers of ISPsystem.