Replies posted by Chadd
Hi Chadd, The screenshot you’re sharing is from Health page which displays the history of the cluster health as well as current issues. As you stated, the error took place and was resolved and so it will remain in the history of the health checks. Unless you see the same error in the Alerts section you can safely ignore this part. The check is event-triggered meaning there will be either no logged check or an error. I can understand how this can confuse things a little bit but also this section is aimed at providing a big picture of cluster health to determine any patterns simultaneous occurrences. It is also up top, will is stay there forever?
Hi @Chadd Under certain conditions, tomcat may fail heartbeats and once this happens 3 consecutive times, the service will restart. If the service restarts 8 times in 4 hours, this alert is raised. You can refer below KB article https://portal.nutanix.com/kb/000008524 May I know the current NCC and AOS version? NCC Version: 22.214.171.124AOS 126.96.36.199 The error only occured on the 28th and we’ve resolved the cause of it, however I do not know how to clear the critical error message
It may not be officially supported, but it can be done. I have three ESXi VMs running on AHV. Each of them have three disks and I was able to create a complete vSAN cluster running the vCenter appliance and a couple of Windows VMs on the vSAN datastore. So far, I haven’t had any issues and its not really all that slow. Obviously, this shouldn’t be used for production, but it allows us to stay up to date with VMware stuff without needing additional hardware. I haven’t tried Hyper-V yet, but maybe that’ll be next. DId you ever get around to trying it in Hyper-V? I’ve been trying but with on luck yet.
Login to the community
Login with your account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.