GitHub user bkrajendra edited a comment on the discussion: Host-HA vs VM-HA
(was: KVMHAMonitor getting initialized without host ha enabled)
CloudStack 4.17.0.1
Recently I also started getting this issue:
```
Apr 27 07:50:33 pnqsun java: WARN [kvm.resource.KVMHAMonitor] (Thread-1:)
(logid:) Write heartbeat for pool [077e9266-fecc-3171-8b1f-6c634ead9ca3]
failed: timeout; stopping
cloudstack-agent.
Apr 27 07:50:33 host java: DEBUG [kvm.resource.KVMHAMonitor] (Thread-1:)
(logid:) Executing:
/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh -i 10.1.
27.14 -p /store0/export/primary -m /mnt/077e9266-fecc-3171-8b1f-6c634ead9ca3 -c
Apr 27 07:50:33 host java: DEBUG [kvm.resource.KVMHAMonitor] (Thread-1:)
(logid:) Executing while with timeout : 60000
Apr 27 07:50:33 host heartbeat: kvmheartbeat.sh will reboot system because it
was unable to write the heartbeat to the storage.
Apr 27 07:53:33 host kernel: Initializing cgroup subsys cpuset
```
This has happened second time in this month - after 2.5 years.
My Issues is after reboot all the VMs were down.
Is there any way we can restart all the VMs when reboot happens.
In my case I don't see any issue with the NFS server, and its accessible.
Should we treat this issue as temporary NFS reachability or is there anything I
should be checking related to NFS host.
GitHub link:
https://github.com/apache/cloudstack/discussions/8953#discussioncomment-9258148
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
