ContributionsMost RecentNewest TopicsMost LikesSolutionsSisense failure after yum update [Linux] Step-by-Step Guide: Run the following command to check the most recent update history: 1. yum history The list with the recent updates and timestamps will open 2. Find the transaction ID you are interested in (probably the latest one) Open the detailed information about that transaction ID (in this example, ID 9) to check what has been installed: 3. yum history info 9 Revert the needed transaction back (in this example, ID 9): 4. yum history undo 9 5. Check if Sisense is up and running again Conclusion: Pay attention to the packages that Sisense is dependent on and also security-related ones that might block some operations. Updates to the packages like Docker, SELinux, and Firewall can potentially cause issues with Sisense operations or access. Additional information about the yum history command: https://access.redhat.com/solutions/64069 https://www.cyberciti.biz/faq/yum-history-command/ 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. 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. Useful helm commands [Linux] How to check Helm charts with “heml” commands. Applies to all on-prem Sisense for Linux versions. Client-server version difference exceeds supported skew (+/-1) How to fix version difference between client (1.xx) and server (1.xx) exceeds the supported minor version skew warning during the upgrade