Article ID: 117944, created on Oct 14, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo


A Virtual Environment does not relocate when the node in Virtuozzo Cluster (Parallels Cloud Storage Cluster) crashes.


Among possible reasons:

  1. High Availability daemon shamand was stopped on the node before the crash.
  2. 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.

  1. Make sure that the shaman join command was executed and you see all nodes in the shaman -c $CLUSTER_NAME stat output:

    # shaman -c pcs stat
     Cluster 'pcs'
     Nodes: 5
     Resources: 8
       NODE_IP      STATUS          RESOURCES    Active          3 CT, 0 VM
    *M    Active          2 CT, 1 VM    Active          1 CT, 0 VM    Active          0 CT, 0 VM    Active          1 CT, 0 VM

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

Related topics

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?

Search Words

high availability

VMs on failed node are not restarted on failover node






0dd5b9380c7d4884d77587f3eb0fa8ef 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF