Changing the hostname on a Raft cluster node

To change the hostname on a Raft cluster node:

  1. On the node where you want to change the hostname, stop all KUMA services by running the following command:

    sudo systemctl stop kuma-

  2. Create a Raft recovery file using the following command:

    touch /opt/kaspersky/kuma/core/<Core_ID>/raft/.reset

  3. Go to the systemd directory with the configuration of the KUMA Core service and change the startup parameters:
    • Specify the new FQDN of the node in the --raft.node.addr option.
    • Remove the --raft.join option if it is specified.
  4. In the systemd configuration files of other services (collector, correlator, storage, event router) change the following settings:
    • In the --core option, specify the new name of the node with the KUMA Core.
    • Specify the new machine name in the --advertise.fqdn option.
  5. Apply the new settings by running the following command:

    sudo systemctl daemon-reload

  6. Change the hostname on the host:

    sudo hostnamectl set-hostname <new_hostname>

  7. In the /etc/hosts file, replace the old hostname with the new one.
  8. Restart the node by running the following command:

    sudo reboot

  9. After the node boots, connect to the node under the new hostname.
  10. Start the KUMA Core service:

    sudo systemctl restart kuma-core-00000000-0000-0000-0000-000000000000.service

  11. Verify that the KUMA web interface is accessible under the new hostname.
  12. Specify the new hostname in the settings of the KUMA storage.
  13. In the KUMA web interface, go to the Resources and services → Active services section, and in the list of services, select the check box for the services that you need, then in the toolbar or in the menu (menu_more_vertical), click Reset certificate.

    KUMA automatically generates a new certificate for each service for which the certificate has been reset. You do not need to restart running services, the new certificate is applied automatically. A stopped service must be restarted to have the new certificate applied.

  14. Delete the directories with service certificates by running the following commands:

    /opt/kaspersky/kuma/<service_name>/<service_ID>/certificates

    /opt/kaspersky/kuma/clickhouse/certificates

  15. Restart all KUMA services:

    sudo systemctl restart kuma-

The KUMA Core node is now working under the new hostname, and the services are displayed in the Resources and services → Active services section with a green status.

Page top