Connection to the slave nodes fails after migration of Master SolusVM node to the new server: Debug Data: ERROR:3

Symptoms

SolusVM Master server cannot connect to the all slave nodes after migration of Master SolusVM node to the new server with the following error in the web interface:

SVM_ERROR: Connection Failed
Debug Data: ERROR:3

Cause

ACL files /usr/local/solusvm/data/allow.dat contain old Master IP on the slaves

Resolution

Note: The article is applicable for the cases with ERROR: 3 code error only. If the code error is different, search for the solution in this hub article

As it is described in SolusVM documentation the steps below should be performed on each slave:

1. Connect to the server via SSH
2. Move allow.dat file to another location:

   # mv /usr/local/solusvm/data/allow.dat /root/

3. In SolusVM web interface open the slave node management page to re-generate this file. Browse to Dashboard > Node > slave_node_name