GitHub user wverleger closed a discussion: Cloudstack 4.19.2.0 - KVM Cloudstack Agent Stuck
Hi, We are running ACS 4.19.2.0 with KVM hypervisors (Ubuntu 24.04 LTS), using linstor as hyperconverged storage and nfs as secondary storage. We have the phenomen, that one of our hosts seems to have a cloudstack agent problem. In the UI the "State" is "Up" and the "Resource state" is "Enabled" of the host but for some reason the agent seems to be unresponsive. We have noticed this because the agent.log stopped working (no new entries and no logrotate) and volume snapshots started to fail and ended in error state. What we also can see is, that the communication to (redundant) virtual routers on this host is disrupted, health checks fail, and the requested host is not repsonding. After failed health checks the router is getting replaced and the old one should be expunged but the router is still in expunging status. I have attached a management-server log entry regarding virtual router "r-749-VM" not able to perform health checks. The cloudstack-agent log on the host is inconspicuous. [cloudstack_management_log.txt](https://github.com/user-attachments/files/19890401/cloudstack_management_log.txt) After restarting the cloudstack-agent the logging starts to work again. But the router state is still "expunging". Has anyone had any experience with it? Does anyone know a good way to troubleshoot? Thanks! BR Wilken GitHub link: https://github.com/apache/cloudstack/discussions/10771 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
