Search results

Ok. Ill do this. Thank you. Anders

Ok. But I removed all HA entries? and had the same result. So I should have one network for corosync, one network for SAN/storage and one network for VM+CT?

Hi, Well I moveed all VM + CT to the other nodes - and they are running nicely hours before. So node1 is totally empty and node2+3 are running fine. Until I down node1. And I did this 3 times - same result. And both node2 and node3 restarts all vm + vt. Corosync and storage - yes they are on...

Hi, I have en 3 node cluster fully upgraded to 6.2 - in production and that works great. VM and CT are on a share storage and HA is great and working. I want to do a memory upgrade of the nodes. When I down my node1 (after moving all vm and ct) the two other nodes seems to fail or restart...

FIXED. Started the two nodes down for maintenance - upgrade them to 5.3-9 - and then the cluster was fine. Downed another node without the "Standalone node - no cluster defined" issue earlier.

A screenshot

Hi, It says "hostname lookup 'blade04' failed - failed to get address info for: blade04: Name or service not known" And Blad04 is down for maintenance. With blade04 on - I still have the same "no cluster" issue.

Hi, I have a Cluster that was fine and now is "Standalone node - no cluster defined" in the GUI. It seems to operate normal. I have some issues that might be related or not (HA seems to be affected). I have upgraded to the latest "5.3-9" and still have the no cluster defined issue...