Did you find a solution for this issue? I am running into the same issue right after updating the CVMs. *EDIT* I had a look at the logs of the management web app and I can see the following: 2024-12-07 16:47:31.787 00017 DEBUG | [RemoteHostClient]: Send GET request: 'https://10.229.0.20/api/v1/pools...

I will reach out to the support email momentarily. Like I said, the nodes were in sync even though the management tcp service was not available. My issue was that the CVM was reporting that the nodes were out of sync (hence limited availability), I assume because they couldn't communicate with each ...

That procedure does not help because the nodes are reported as "Not Synchronized" in the CVM and the starwind-virtual-san is not listening on port 3261 on either nodes. What I did today was stop the starwind-virtual-san on the 2nd node, restart startwind-virtual-san on the first node, usin...

That's the thing, it's dead. There's no way to connect to it back. To be able to restore connectivity I have to take down the whole cluster, stop the starwind-virtual-san service on all nodes, start starwind-virtual-san on the node I know is up to date, mark it as synchronized, start the starwind-vi...

While I understand that the issue might be the vulnerability scanner (that is still not confirmed, anyway), because of the current landscape more and more people will do this sort of scans and end up in my situation. More over, unless the vulnerability scanner has some NVT specific to Starwind manag...

Hello! We have set up the vSAN CVM Free version with two ESXi 7 nodes in the cluster with heartbeat synchronization. Everything works great with the exception of the management ports randomly dies. By the management port I meant 3261. This is the second time I find that the wine process that normall...