Case Studies

Problem: The client was operating Jenkins 2.344 on Apache Tomcat 8.5.41 and required redirection from port 8084 (HTTP) to port 8443 (HTTPS). Although the “server.xml” and “web.xml” files were configured in the $CATALINA_HOME/conf/ directory, leading to successful redirection from http://jenkins:8084 to https://jenkins:8443, accessing http://jenkins:8084/jenkins (the application) did not redirect to port 8443. The cancellation of […]

Problem: The client’s production Apache Cassandra cluster experienced sudden native transport failure, leading to significant operational impact. Despite efforts to diagnose the problem using system logs and debug logs, the root cause remained unidentified. Native transport errors, particularly SSLPeerUnverifiedException, were prevalent in the debug logs, indicating authentication failures for multiple nodes in the cluster. Process: […]

Problem: The client, deploying the Prometheus operator using a community helm chart, encountered a security concern regarding the permissions granted to the Prometheus operator. Upon closer examination, it was discovered that the community helm chart provided overly permissive access rights, particularly with ‘*’ permissions for secrets and configmaps, as well as delete permissions for default […]

Problem: The client is experiencing daily automatic restarts of their Cassandra database, potentially causing issues with application connectivity. Additionally, they’re encountering errors related to JVM memory, degraded mode, connection resets by peer, and null pointer exceptions on indexes. Solution: After a thorough analysis of the provided logs, the following findings and recommendations were made: Identify […]

Problem: The client encountered a recurring issue within the Docker Swarm environment, wherein containers sporadically crashed with exit code 137. This behavior, indicative of potential memory-related issues, was exacerbated by the absence of corresponding container logs, complicating the diagnostic process. Process: Initial Inquiry and Investigation: Prompted by the client’s request for a Root Cause Analysis […]

Problem: A client with an Elasticsearch cluster consisting of three nodes was experiencing a recurring issue where one of the nodes is disconnecting from the cluster automatically. This disruption was resulting in numerous unassigned shards, impacting the overall stability and performance of the Elasticsearch environment. Process: Data Collection for Further Analysis: Request: Provide detailed system […]

Problem: The client’s Elastic server is experiencing sporadic crashes, evident from StackOverflowError logs linked to “GraphTokenStreamFiniteStrings.” While a potential fix exists in Lucene 9.7, the product’s certification with Elastic 7.17 using Lucene 8.11.1 complicates the implementation of the fix. The client seeks assistance to evaluate the possibility of backporting Lucene 9.7 changes to Lucene 8.11.1. […]

Problem: The problem identified in Apache Airflow version 2.5.0 was the lack of password confirmation during password changes, posing a significant security risk to users. This vulnerability could potentially lead to unauthorized access and session hijacking within the Airflow application. Solution: Based on the client’s request and the provided information, the recommended solution steps to […]

Problem: The client reported instances of Cassandra databases experiencing unavailability and performance degradation, leading to application connection errors. Specifically, nodes were found to be unresponsive, and memory and CPU utilization spiked unexpectedly. Additionally, there were concerns about data inconsistencies between data centers and excessive tombstones affecting performance. Process: Initial Investigation: Upon initial investigation, it was […]