Updating previous versions of KUMA

To install KUMA version 2.1.x over version 2.0.x, complete the preliminary steps and then update.

Preliminary steps

1. Creating a backup copy of the KUMA Core.
2. Make sure that all application installation requirements are met.
3. Make sure that MongoDB versions are compatible by running the following sequence of commands on the device where KUMA Core is located:

   cd /opt/kaspersky/kuma/mongodb/bin/

   ./mongo

   use kuma

   db.adminCommand({getParameter: 1, featureCompatibilityVersion: 1})

   If the component version is different from 4.4, set the value to 4.4 using the following command: 

   db.adminCommand({ setFeatureCompatibilityVersion: "4.4" })

4. During installation or update, ensure network accessibility of TCP port 7220 on the KUMA Core for the KUMA storage hosts.
5. If you have a keeper deployed on a separate device in the ClickHouse cluster, install the storage service on the same device before performing the update:
   • Use the existing storage of the cluster to create a storage service for the keeper in the web interface.
   • Install the service on a device with a dedicated ClickHouse keeper.
6. In the inventory file, specify the same hosts that were used when installing KUMA version 2.0.X. Set the following settings to false:

   deploy_to_k8s false

   need_transfer false

   deploy_example_services false

   When the installer uses this inventory file, all KUMA components are upgraded to version 2.1.0. The available services and storage resources are also reconfigured on hosts from the kuma_storage group:

   • ClickHouse systemd services are deleted.
   • Certificates are deleted from the /opt/kaspersky/kuma/clickhouse/certificates directory.
   • The Shard ID, Replica ID, Keeper ID, and ClickHouse configuration override fields are filled in for each node in the storage resource based on values from the inventory and configuration files of the service on the host. Subsequently, you will manage the roles of each node in the KUMA web interface.
   • All existing configuration files from the /opt/kaspersky/kuma/clickhouse/cfg directory are deleted (they will be subsequently generated by the storage service).
   • The value of the LimitNOFILE parameter (Service section) is changed from 64,000 to 500,000 in the kuma-storage systemd services.
7. If you use alert segmentation rules, prepare the data for migrating the existing rules and save. In the next step, you can use this data to re-create the rules. During the update, alert segmentation rules are not migrated automatically.
8. To perform an update, you need a valid password from the admin user. If you forgot the admin user password, contact Technical Support to reset the current password and use the new password to perform the update at the next step.

Updating KUMA

1. If you have a ready-made inventory file, follow the instructions for distributed installation of the program.

   If an inventory file is not available for the current version, use the provided inventory file template and fill in the corresponding settings. To view a list of hosts and host roles in the current KUMA system, in the web interface, go to Resources → Active services section.

2. When upgrading on systems that contain large amounts of data and are operating with limited resources, the system may return the 'Wrong admin password' error message after you enter the administrator password. If you specify the correct password, KUMA may still return an error because KUMA could not start the Core service due to a timeout error and resource limit. If you enter the administrator password three times without waiting for the installation to complete, the update may end with a fatal error. Resolve the timeout error to proceed with the update.

The final stage of preparing KUMA for work

1. After updating KUMA, you must clear your browser cache.
2. Re-create the alert segmentation rules.
3. Manually update the KUMA agents.

KUMA update completed successfully.

To install KUMA version 2.1.3 over version 2.1.x, complete the preliminary steps and then update.

Preliminary steps

1. Creating a backup copy of the KUMA Core.
2. Make sure that all application installation requirements are met.
3. During installation or update, ensure network accessibility of TCP port 7220 on the KUMA Core for the KUMA storage hosts.
4. To perform an update, you need a valid password from the admin user. If you forgot the admin user password, contact Technical Support to reset the current password and use the new password to perform the update at the next step.

Updating KUMA

1. If you have a ready-made inventory file, follow the instructions for distributed installation of the program.

   If an inventory file is not available for the current version, use the provided inventory file template and fill in the corresponding settings. To view a list of hosts and host roles in the current KUMA system, in the web interface, go to Resources → Active services section.

2. When upgrading on systems that contain large amounts of data and are operating with limited resources, the system may return the 'Wrong admin password' error message after you enter the administrator password. If you specify the correct password, KUMA may still return an error because KUMA could not start the Core service due to a timeout error and resource limit. If you enter the administrator password three times without waiting for the installation to complete, the update may end with a fatal error. Resolve the timeout error to proceed with the update.

The final stage of preparing KUMA for work

1. After updating KUMA, you must clear your browser cache.
2. Manually update the KUMA agents.

KUMA update completed successfully.