18:00 UTC today to avoid automated failover.
If no conflict is found, run tserverhq-diagnostic --full and share the output.
We also recommend checking the RAID controller logs for any predictive failures. tserverhq
Let me know if you need assistance accessing the IPMI console.
The monitoring system flagged irregular I/O latency on tserverhq-03 between 02:15–02:45 UTC. Disk utilization spiked to 98%, but CPU and memory remained within normal ranges. 18:00 UTC today to avoid automated failover
Server Health & Action Required – Node tserverhq-03
Initial logs suggest a possible backup job collision with the nightly aggregation script. Please review the cron schedules for both processes and confirm if they can be staggered by at least 20 minutes. tserverhq
— Ops