Troubleshooting Pods in Kubernetes ClustersIn Kubernetes, pods can encounter various issues that prevent them from running correctly. Understanding the different pod states and how to troubleshoot them is essential for maintaining a healthy cluster. ...
Resolving Issues with Updating EC2EC Passwords in Elasticube Connections Summary This article addresses the issue of updating EC2EC (Elasticube to Elasticube) passwords in the context of employee off-boarding or password changes. Specifically, it c...
Resolving Installation Failures with "Error occurred during validate_ssl_certs section" Issue: During the installation process on a Linux system, you may encounter the error message: "Error occurred during validate_ssl_certs section." This error typ...
Installation fails with /bin/activate: No such file or directory Sisense installation may fail in the very beginning with the following symptoms: [2024-06-18 18:07:02] Preparing System ...[2024-06-18 18:07:02] Linux user: sistemas[2024-06-18 18:07:0...
Network Error: Pending Operation: Update Model Layout You receive the following alert: Add data Network error: Response not successful: Received status code 400 Pending operation: Update model layout during the process of updating the table quer...
Fixing the File Manager When It's Not Working for Tenant Admins Despite the "File Manager" being enabled in the "Feature Management" menu and working properly for the System tenant admins, the tenant admins receive the "Access Forbidden" error on th...
Restoring missing connector Introduction Sometimes connectors can go missing for some reason, leading to a breakdown in data connectivity. Restoring these connectors is crucial to maintaining a smooth data flow within your Sisense environment. This...
There is a known issue that is planned to be fixed in the Sisense L2023.6+. If you install Sisense on CentOS or RHEL version >= 8 the old EPEL 7 repositories are used instead of EPEL 8 To fix this issue: Locate in the installation folder and open i...
If you see the following errors in the installation log: failed: [node1] (item=10250) => {"changed": false, "elapsed": 2, "item": "10250", "msg": "Timeout when waiting for 127.0.0.1:10250 to stop."} failed: [node1] (item=10248) => {"changed": fal...
