Knowledge Base

Problem: A production Patroni-managed PostgreSQL 15.17 cluster (Patroni 3.3.2) reported persistent high memory consumption on database VMs, frequently exceeding 80% of allocated RAM and once reaching ~95% on a previous 300GB node. The deployment uses max_connections=4000 (cannot be reduced by the application), huge_pages configured as on with approximately 60,000 pages reserved, and vm.overcommit_memory=2 set per […]

Problem: A three-site RabbitMQ cluster experienced frequent incidents where a single site would become “stuck” and this state would cause all three sites to stop processing. The customer reported that one node would intermittently become unresponsive for varying reasons and that after that event, publishers and consumers across the cluster were blocked until manual intervention. […]

Problem: A Patroni-managed PostgreSQL cluster showed recurring replication interruptions: the replica repeatedly reported a large streaming lag (initially ~565 MB, later observed ~5.5 GB) and the cluster’s physical replication slot on the leader appeared inactive (active = false, wal_status = reserved). Patroni logs on the primary had not recorded recent cluster events and appeared to […]

Problem: A three-site RabbitMQ cluster experienced frequent incidents where a single site would become “stuck” and that condition then caused the entire three-site cluster to block. Symptoms reported included intermittent node unresponsiveness, client operations timing out or hanging, and cluster-wide stalls that required manual intervention to recover. The environment was a geographically distributed, multi-site RabbitMQ […]

Problem: A production security scan flagged CVE-2026-42945 in the Kubernetes ingress controller image. The customer reported use of ingress-nginx/controller:v1.12.1 and also verified the issue exists in ingress-nginx/controller:v1.15.1. The scan result and customer concern described this CVE as a high-severity security exposure affecting live traffic handling in production clusters. The deployment used upstream community controller images […]

Problem: The customer reported that deployed container images nginx:1.31 and nginx:1.31.2 contained a high-severity vulnerability: CVE-2026-55200 (libssh2) with a reported CVSS score of 8.3. Their inventory showed the images were based on Debian 13 (trixie) and the finding originated from a packaged libssh2 version present inside the image. No production outage was reported; the request […]