https://systemsgolive.com/categories/troubleshooting/Recent content in Troubleshooting on SystemsGoliveHugo -- gohugo.ioen© 2026 systemsgolive.com and Mickael Asghar. All rights reserved.Tue, 03 Mar 2026 14:30:34 +0000https://systemsgolive.com/post/fixing-ldap-after-vm-snapshot/Tue, 03 Mar 2026 14:30:34 +0000https://systemsgolive.com/post/fixing-ldap-after-vm-snapshot/ Resolving an OpenLDAP service failure on a VM snapshot — fixing hostname identity mismatches, loopback address issues, olcServerID with CRC32 recalculation, and removing leftover replication config from the source server.https://systemsgolive.com/post/implementating-backup-ping-monitoring-solution/Tue, 10 Sep 2024 16:44:01 +0100https://systemsgolive.com/post/implementating-backup-ping-monitoring-solution/ On Friday 6th September 2024 at 21:31, we received an alert from LogicMonitor indicating one of our production web app servers (Tomcat#3) was down, with the message: "The host Tomcat#3 (i-xxxxxxx) is down". However, shortly after receiving the alert, we attempted to SSH into the VM and confirmed that the server was fully operational. But what did it go wrong?https://systemsgolive.com/post/logicmonior-cpubusypercent-alert/Fri, 23 Aug 2024 22:05:29 +0100https://systemsgolive.com/post/logicmonior-cpubusypercent-alert/ On 15th August 2024, an incident occurred where the `CPUBusyPercent` alert did not trigger for one of our Production MySQL Database VMs (DB01), despite the CPU being at 100% for seven minutes. This was unexpected since the threshold settings in LogicMonitor were supposed to trigger alerts under such conditions.