Beyond the Spooler & Snapshots: Resolving Wazuh Agent Fleet Mismatch & Configuration Drift in a Distributed Homelab
1. Who (Who Was Affected?) As a systems administrator and IT infrastructure consultant operating an extensive self-hosted homelab ecosystem—comprising 20+ nodes including Proxmox VMs, LXCs, Dell OptiPlex Micro servers, and industrial systems—maintaining robust security and reliable agent telemetry is paramount. The degradation directly impacted our core infrastructure monitoring visibility and threat detection capabilities across the entire network. 2. What (What Was the Issue?) The entire wazuh-agent fleet experienced sudden, widespread failures, persistently throwing Disconnected statuses despite prior automated deployments. The primary symptoms included: Daemon Exit Errors: The wazuh-agent.service repeatedly crashed due to XML parsing and validation errors within ossec.conf (specifically concerning syscheck/FIM blocks) following an attempted upgrade to a newer release ( v4.14.10 ). State & ID Mismatch: Proxmox VM and LXC snapshot rollbacks inadvertently reintroduced...