Error in ingress-nginx-controller pod after upgrading Sisense to L2024.1
Error in ingress-nginx-controller pod after upgrading Sisense to L2024.1: main.go:64] port 80 is already in use. Please check the flag --http-port !NOTE! - this guide is relevant for non-cloud managed Sisense deployments i.e. installed with Sisense Kubernetes (RKE). After upgrading Sisense to version L2024.1 you might face the following error in ingress-nginx-controller pod’s logs (the default namespace): main.go:64] port 80 is already in use. Please check the flag --http-port Such an issue might be the result of incompatibility between the ingress-Nginx release version that was updated in Sisense L2024.1 and the Kubernetes version in case it is lower than v1.26. In case Sisense L2024.1 was freshly installed on the non-cloud instance (i.e. with Sisense RKE) as a fresh deployment (and was not upgraded from the previous version) this issue should not reveal since L2024.1 package already comes with v1.26 Kubernetes by default. However, if Sisense was upgraded to L2024.1 or it was deployed/installed on Kubernetes lower than v1.26 there will be an incompatibility between the ingress-Nginx release implemented in L2024.1 (4.10.0). To resolve the issue it is necessary to re-run the Sisense upgrade with the following parameters in the configuration yaml file: update: true update_k8s_version: true In case you are still facing the same issue after that, please open a ticket for Sisense Support. This article provides a brief explanation regarding possible Nginx<->Kubernetes compatibility issues in Sisense L2024.1. The article also provides the steps to resolve the issue described. 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.
Error on installation "cp: cannot create regular file '/usr/local/bin/kubectl': Text file busy"
The error "cp: cannot create regular file '/usr/local/bin/kubectl': Text file busy" typically occurs when multiple upgrade processes are running simultaneously, causing a conflict when trying to update the kubectl binary. [2024-10-30 12:33:34] Getting binaries kubectl (v1.30.3) and helm (v3.12.3) [2024-10-30 12:33:34] Downloading them from the internet % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 138 100 138 0 0 1367 0 --:--:-- --:--:-- --:--:-- 1380 100 49.0M 100 49.0M 0 0 3478k 0 0:00:14 0:00:14 --:--:-- 3525k % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 15.2M 100 15.2M 0 0 3730k 0 0:00:04 0:00:04 --:--:-- 3731k linux-amd64/helm cp: cannot create regular file '/usr/local/bin/kubectl': Text file busy [2024-10-30 12:33:53] ** Error occurred during command sudo cp installer/05_post_infra/files/kubectl installer/05_post_infra/files/helm /usr/local/bin section ** [2024-10-30 12:33:53] ** Exiting Installation ... ** For example, in one case, the error occurred because multiple upgrades were happening on the same environment simultaneously (the same bastion for several cloud environments), which led to the Kubectl binary being in use by another upgrade process. The recommended solution is to check if any process is using Kubectl or Helm before proceeding with the upgrade. Watching an upgrade with "kubectl ... -w" command can cause this issue also. To prevent this error, it is advisable to: Ensure that no other upgrade or deployment processes are running in parallel. Use commands like lsof -t $(which kubectl) and lsof -t $(which helm) to check if these binaries are in use. If any command returns a PID, print out the process details using ps -ef | grep <pid number> and fail the pipeline if necessary. By following these steps, you can avoid the "Text file busy" error and ensure a smooth upgrade process. Related Content: https://academy.sisense.com/sisense-administration https://docs.sisense.com/main/SisenseLinux/upgrading-sisense.htmInstallation Problem. License server is unavailable
Question: I am trying to download and install Sisense but when I do, it says the license server is unavailable. Answer: If your license is up do date, please take the following steps: Within the Windows menu, search for Sisense Activation, then right click 'Run as Administrator' Take note of the email address your account is set up under (you will need the password when you log back in) Sign out of your Sisense account Close Sisense Activation Stop and Restart the Sisense.Oxygen service by doing the following: Open the Control Panel Administrative tools Services Locate the Sisense.Oxygen service and right-click and select Stop to stop it Then, right-click and select Start to start it 6. Then reopen and log back into Sisense Activation If these steps do not help, please create a ticket and our support team is happy to help you out.Install Issues - Stuck on "Downloading Sisense Licensing Server"
Question: Sisense installation on Windows server stuck at 20% install and then the installer fails: In the %temp% install logs we saw the following errors: Error 0x80070570: Failed to extract all files from container, erf: 1:4:0 Error 0x80070570: Failed to begin and wait for operation. Error 0x80070570: Failed to extract payload: a3 from container: WixAttachedContainer Answer: This error indicates a corrupted install file or inability to access the %temp% folder where the extracted install files are temporarily written to. The file could be corrupted from copying from another machine or by antivirus software installed on the machine when downloading the installer. Often this issue can be resolved by re-downloading the install file directly to the server from this list: Sisense Release Versions. Before re-running the installer it is also recommended to remove the Sisense folder from %ProgramData% and %ProgramFiles%. If these steps do not resolve the issue, please create a support ticket and our TSE team will be able to assist.Unable to sign out from my existing license login - Sign out failed
Question: When I'm trying to sign out from my existing login. It shows a warning alert "Sign out failed". Answer: This error might happen when Sisense Activation is not run with administrator privileges. To fix this error please try the following: Search for "Sisense Activation" in your programs on your server/computer you're running Sisense Right click on Sisense Activation and select "Run as Administrator" Try signing out again If that does not allow you to sign out of your Sisense account, please create a support ticket and our support agents would be happy to help.Sisense Linux Multinode: MongoDB, Zookeeper and Data Recovery
There are situations where a Sisense Linux Multinode instance can become corrupted and the only choice to move forward is reinstallation. Sometimes in these cases, users can face a couple of challenges, especially in cases where there is no backup to recreate the instance. In this article, we will review methods that will help to revive data if a user has active storage in MongoDB or Zookeeper.
