Knowledge Base Article

Fresh installation failure [Linux]

This guide walks you through the steps to understand the cause of this error and provides practical fixes to successfully complete the installation.

When performing a fresh installation of Sisense on a new server, you may encounter the following issue during the RKE2 installation step:

[2025-08-19 09:48:39] Detecting Host OS  ...
lsb_release is /usr/bin/lsb_release
[2025-08-19 09:48:39] OS: Ubuntu, Version: 24.04
[2025-08-19 09:48:39] Installing RKE2 server
\[INFO]  using v1.33.0+rke2r1 as release
[INFO]  downloading checksums at https://github.com/rancher/rke2/releases/download/v1.33.0%2Brke2r1/sha256sum-amd64.txt
Stderr: Warning: Permanently added '192.168.20.30' (ED25519) to the list of known hosts.
curl: (23) client returned ERROR on write of 1369 bytes
[2025-08-19 09:48:39] [0;31m** Failed Installing RKE2 server at node sisense-udev (Internal IP: 192.168.15.33). **[0m
[2025-08-19 09:48:39]
[2025-08-19 09:48:39] [0;31m** RKE2 installation failed. **[0m
[2025-08-19 09:48:39] Errors from host 192.168.15.33:
Warning: Permanently added '192.168.15.33' (ED25519) to the list of known hosts.
curl: (23) client returned ERROR on write of 1369 bytes
[2025-08-19 09:48:39] [0;31m** Failed Installing RKE2 server at node sisense-udev (Internal IP: 192.168.15.33). **[0m
[2025-08-19 09:48:39] [0;31m** Error occurred during RKE2 installation section **[0m
[2025-08-19 09:48:39] [0;31m** Exiting Installation ... **[0m

This guide walks you through the steps to understand the cause of this error and provides practical fixes to successfully complete the installation.

Step-by-Step Guide: 

The issue arises when the non-default package manager is used to install utilities needed for the installation. 

In this case, the “curl” utility was installed with the “sudo snap install curl” command

Fix:

  1. sudo snap remove curl
  2. sudo apt install curl

Conclusion

Use the default package managers for certain OSes to avoid issues like this one

Additional information about this issue:

Sisense prerequisites that should be followed before each installation:

Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.

Published 09-18-2025
No CommentsBe the first to comment