Wondering how to fix SolusVM Connection Failed Debug Data: ERROR:3? We can help you!
SolusVM users report to us that often the connection to the slave nodes fails after migration of the Master SolusVM node to the new server followed by this error.
Here at Bobcares, we handle requests from our customers to fix similar errors as a part of our Server Management Services.
Today let’s see how our Support Engineers fix this issue for our customers.
How to fix SolusVM “Connection Failed Debug Data: ERROR:3”
Before going into the steps for fixing the error we will see what causes this error.
We will see the following error in the web interface:
When the ACL files /usr/local/solusvm/data/allow.dat contain old Master IP on the slaves, it can trigger this error. Also, we will get “Cannot connect, Please check your connection settings” while trying to add slave node to SolusVM Master Panel.
Steps to fix this error:
The following steps must be performed on each slave node:
1. First we have to connect to the server via SSH
2. Then we have to move allow.dat file to another location. For this we can use the following command:
# mv /usr/local/solusvm/data/allow.dat /root/
3. After that, in the SolusVM web interface we have to open the slave node management page to re-generate this file.
Furthermore, we can fix the “Cannot connect, Please check your connection settings” error using the following steps:
1. Firstly, we have to connect to the slave node via SSH
2. Then remove the file as given below:
# rm -f /usr/local/solusvm/data/allow.dat
3. After that we have to restart the web service:
# service lighttpd restart && service svmstack-nginx restart
4. Now we can use the data from /usr/local/solusvm/data/solusvm.conf to connect Slave Server to master node.
For this, we have to take SolusVM and go to Nodes, click Add Node.
[Need assistance? We can help you]
To conclude, we saw the steps that our Support Techs follow to fix SolusVM “Connection Failed Debug Data: ERROR:3” for our customers.