A Virtual Environment does not relocate when the node in Virtuozzo Cluster (Parallels Cloud Storage Cluster) crashes.
Among possible reasons:
- High Availability daemon
shamandwas stopped on the node before the crash.
- Virtuozzo node was not joined shaman cluster before crash.
In order to guarantee the resources relocation on server unavailability, it is required that
shamand service is configured appropriately.
Make sure that the
shaman joincommand was executed and you see all nodes in the
shaman -c $CLUSTER_NAME statoutput:
# shaman -c pcs stat Cluster 'pcs' Nodes: 5 Resources: 8 NODE_IP STATUS RESOURCES 10.1.2.11 Active 3 CT, 0 VM *M 10.1.2.12 Active 2 CT, 1 VM 10.1.2.13 Active 1 CT, 0 VM 10.1.2.14 Active 0 CT, 0 VM 10.1.2.15 Active 1 CT, 0 VM ---snip---
2.Check the state of the shamand on the faulty node, start it if is is stopped:
~# service shamand status ~# service shamand start
Also, ensure that
shamand will be started automatically after node restart with the following command:
~# chkconfig shamand on
117939 Containers and virtual machines are not relocated after server reboot/shutdown
125249 Virtual environments did not relocate on SPARE node after crash
119207 Tuning Parallels Cloud Storage High Availability Cluster configuration.
119300 How can I track the movement of resources in a high availability cluster on Parallels Cloud Storage after a node crash?