Troubleshooting update errors

When updating KUMA, you may encounter the following errors:

• Timeout error

  When upgrading from version 2.0.x 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 resource limit and a timeout error. If you enter the administrator password three times without waiting for the installation to complete, the update may end with a fatal error.

  Follow these steps to resolve the timeout error and successfully complete the update:

  1. Open a separate second terminal and run the following command to verify that the command output contains the timeout error line:

     journalctl -u kuma-core | grep 'start operation timed out' 

     Timeout error message:

     kuma-core.service: start operation timed out. Terminating.

  2. After you find the timeout error message, in the /usr/lib/systemd/system/kuma-core.service file, change the value of the TimeoutSec parameter from 300 to 0 to remove the timeout limit and temporarily prevent the error from recurring.
  3. After modifying the service file, run the following commands in sequence:

     systemctl daemon-reload

     service kuma-core restart

  4. After executing the commands and successfully starting the service in the second terminal, enter the administrator password again in the original first terminal when the installer prompts you for the password.

     KUMA will continue the installation. In resource-limited environments, installation may take up to an hour.

  5. After installation finishes successfully, in the /usr/lib/systemd/system/kuma-core.service file, set the TimeoutSec parameter back to 300.
  6. After modifying the service file, run the following commands in the second terminal:

     systemctl daemon-reload

     service kuma-core restart

  After the commands are executed, the update will be completed.

• Invalid administrator password

  The admin user password is required to automatically populate the storage settings during an update. If you entered an incorrect admin user password nine times during the TASK [Prompt for admin password], the installer still performs the update, and the web interface is still available. However, the storage settings are not migrated, and the storages will show a red status.

  To fix the error and make the repositories available for use, update the storage settings:

  1. Go to the storage settings, manually fill in the ClickHouse cluster fields, and click Save.
  2. Restart the storage service.

  The storage service will start with the specified parameters and will show a green status.

• DB::Exception error

  After updating KUMA, the storage may be in a red status, and its logs may show errors about suspicious strings.

  Example error:

  DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, int, bool) @ 0xda0553a in /opt/kaspersky/kuma/clickhouse/bin/clickhouse

  To restart ClickHouse, carry out the following command on the KUMA storage server:

  touch /opt/kaspersky/kuma/clickhouse/data/flags/force_restore_data && systemctl restart kuma-storage-<ID of the storage where the error was detected>

Fix the errors to successfully complete the update.